Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 6b67480845126bf8a2da2dcdf0677add376038dd1437a3b9926eb418671214b6

Tx prefix hash: cd47e59ac860561a82a6b92a7db7c4eaf9446730b5525b4200c34ded3c39ea68
Tx public key: 6cbec8e6d792c0a2061d701a37c8bce30b666df1102c3f21dee4ecb0d4584ef6
Timestamp: 1751579453 Timestamp [UCT]: 2025-07-03 21:50:53 Age [y:d:h:m:s]: 00:128:19:14:04
Block: 1318200 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 90303 RingCT/type: yes/0
Extra: 016cbec8e6d792c0a2061d701a37c8bce30b666df1102c3f21dee4ecb0d4584ef6021100000004dfc3ba49000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b8f4740e5521b297eb0e96b636e3e033270937e56ee0bfd3a2a19293634e7691 0.600000000000 1805877 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": 1318210, "vin": [ { "gen": { "height": 1318200 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b8f4740e5521b297eb0e96b636e3e033270937e56ee0bfd3a2a19293634e7691" } } ], "extra": [ 1, 108, 190, 200, 230, 215, 146, 192, 162, 6, 29, 112, 26, 55, 200, 188, 227, 11, 102, 109, 241, 16, 44, 63, 33, 222, 228, 236, 176, 212, 88, 78, 246, 2, 17, 0, 0, 0, 4, 223, 195, 186, 73, 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