Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 881cd57ae145a3efa549c4e02393972974b0bcf7fe1432b41b4b59a4b6476c97

Tx prefix hash: 13411980bd9e44995b7e7856ab055e808b8b2b0d035c45cd3728711d38ac3f9d
Tx public key: 521db2876a1c43e0e5ef189a759b029a00fb547c329ee5fe7a01f197eaa44f37
Timestamp: 1745252004 Timestamp [UCT]: 2025-04-21 16:13:24 Age [y:d:h:m:s]: 00:023:08:08:28
Block: 1266393 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 16705 RingCT/type: yes/0
Extra: 01521db2876a1c43e0e5ef189a759b029a00fb547c329ee5fe7a01f197eaa44f370211000000086c98aa3d000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 01ff592d00bfd25f923038a3b0572828aa49311c990a02714bb644b2faa50115 0.600000000000 1753614 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": 1266403, "vin": [ { "gen": { "height": 1266393 } } ], "vout": [ { "amount": 600000000, "target": { "key": "01ff592d00bfd25f923038a3b0572828aa49311c990a02714bb644b2faa50115" } } ], "extra": [ 1, 82, 29, 178, 135, 106, 28, 67, 224, 229, 239, 24, 154, 117, 155, 2, 154, 0, 251, 84, 124, 50, 158, 229, 254, 122, 1, 241, 151, 234, 164, 79, 55, 2, 17, 0, 0, 0, 8, 108, 152, 170, 61, 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