Dinastycoin Explorer Dinastycoin Blockchain Explorer

(no javascript - no cookies - no web analytics trackers - no images - open sourced)

Autorefresh is OFF

Tx hash: 664bf6d1b3fea9597b7ae008d806694b8442eb97f7caeb5ffd4972e6ba11cf6a

Tx prefix hash: da83036f705f2703cb3e762521d3fa53abbaeef4b0f62a732d4f731325b385e2
Tx public key: 524a791828dca6fadd3c018ec7b497bd70d8ee342bc405e112e55e424411bef3
Timestamp: 1770924592 Timestamp [UTC]: 2026-02-12 19:29:52 Age [y:d:h:m:s]: 00:086:04:51:47
Block: 1476406 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 54311 RingCT/type: yes/0
Extra: 01524a791828dca6fadd3c018ec7b497bd70d8ee342bc405e112e55e424411bef3021100000003e4f5193f000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 19009a09c0711c994c8797c6463f43355847ea1963d98324040e9b16be21554b 0.000600000000 1965712 of 15 -

Check which outputs belong to given dinastycoin address/subaddress and viewkey

For RingCT transactions, outputs' amounts are also decoded
Note: address/subaddress and viewkey are sent to the server, as the calculations are done on the server side



Prove to someone that you have sent them dinastycoin in this transaction

Tx private key can be obtained using get_tx_key command in dinastycoin-wallet-cli command line tool
Note: address/subaddress and tx private key are sent to the server, as the calculations are done on the server side



{ "version": 2, "unlock_time": 1476416, "vin": [ { "gen": { "height": 1476406 } } ], "vout": [ { "amount": 600000000, "target": { "key": "19009a09c0711c994c8797c6463f43355847ea1963d98324040e9b16be21554b" } } ], "extra": [ 1, 82, 74, 121, 24, 40, 220, 166, 250, 221, 60, 1, 142, 199, 180, 151, 189, 112, 216, 238, 52, 43, 196, 5, 225, 18, 229, 94, 66, 68, 17, 190, 243, 2, 17, 0, 0, 0, 3, 228, 245, 25, 63, 0, 0, 0, 0, 0, 0, 0, 0, 0 ], "rct_signatures": { "type": 0 } }


Less details
source code | explorer version (api): devel-2026-02-02-6303d2a (1.2) | monero version: