Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4601d59a9934efc29926ccf942e37ee4bd2dbc1af989192dc1710cd2f5cb0a54

Tx prefix hash: fb6f54eeae1e2374836df211ea39a877842efac8809373c7886c0a12f57adee7
Tx public key: 35cce269cabf4917b45e2ebd249446de4e7d6ef6f8e86a82e8ecdec7766c14ec
Timestamp: 1757199763 Timestamp [UCT]: 2025-09-06 23:02:43 Age [y:d:h:m:s]: 00:113:18:05:52
Block: 1362948 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 81356 RingCT/type: yes/0
Extra: 0135cce269cabf4917b45e2ebd249446de4e7d6ef6f8e86a82e8ecdec7766c14ec021100000007b2f784c4000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: c49f6212b7d7aa954a5cb1cf217275e64d3f79940b09f7a47cca85bb629dd10b 0.600000000000 1850987 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": 1362958, "vin": [ { "gen": { "height": 1362948 } } ], "vout": [ { "amount": 600000000, "target": { "key": "c49f6212b7d7aa954a5cb1cf217275e64d3f79940b09f7a47cca85bb629dd10b" } } ], "extra": [ 1, 53, 204, 226, 105, 202, 191, 73, 23, 180, 94, 46, 189, 36, 148, 70, 222, 78, 125, 110, 246, 248, 232, 106, 130, 232, 236, 222, 199, 118, 108, 20, 236, 2, 17, 0, 0, 0, 7, 178, 247, 132, 196, 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