Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b433b0d4fe3ef540a226781477c8f9c05fa2f1f919c189780d9c7e389b3b3db5

Tx prefix hash: d220ad0acd32571a6c7eccf3151c1c573a69780fa4c495eafea669c9c4697d8a
Tx public key: dfb0ad480613e982a66b7439c983701ca2bd7f00dac54b9186cf43d56925a9d3
Timestamp: 1766182123 Timestamp [UCT]: 2025-12-19 22:08:43 Age [y:d:h:m:s]: 00:002:10:20:59
Block: 1437293 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 1736 RingCT/type: yes/0
Extra: 01dfb0ad480613e982a66b7439c983701ca2bd7f00dac54b9186cf43d56925a9d30211000000077b1e51ac000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 664a1d93bffb8e1e1033c567ef504a86bcdec792fc416ea026ee229b36f2610d 0.600000000000 1926100 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 dinasty-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": 1437303, "vin": [ { "gen": { "height": 1437293 } } ], "vout": [ { "amount": 600000000, "target": { "key": "664a1d93bffb8e1e1033c567ef504a86bcdec792fc416ea026ee229b36f2610d" } } ], "extra": [ 1, 223, 176, 173, 72, 6, 19, 233, 130, 166, 107, 116, 57, 201, 131, 112, 28, 162, 189, 127, 0, 218, 197, 75, 145, 134, 207, 67, 213, 105, 37, 169, 211, 2, 17, 0, 0, 0, 7, 123, 30, 81, 172, 0, 0, 0, 0, 0, 0, 0, 0, 0 ], "rct_signatures": { "type": 0 } }


Less details
source code | explorer version (api): master-2022-04-20-3036769 (1.2) | dinastycoin version: 4.1-b41cfa2b8