Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 42211786af2a55c5fca0263740e2c8bee40f8b43ecae99e27f7010570bada94c

Tx prefix hash: 981c6513e48e79e27bd03dc2ef6383d544fd011c65e242c28df61dff8d2643d0
Tx public key: a35c2c3d6d01b93170d313480bbecf0e51c631f6f2ee0ea767f130e8cc860d00
Timestamp: 1764172633 Timestamp [UCT]: 2025-11-26 15:57:13 Age [y:d:h:m:s]: 00:000:16:00:00
Block: 1420640 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 479 RingCT/type: yes/0
Extra: 01a35c2c3d6d01b93170d313480bbecf0e51c631f6f2ee0ea767f130e8cc860d000211000000014e7bfc09000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a96ef699147ba9a9d53012c9bf11f0103485539a6c98f96bab77b8512f33b4f0 0.600000000000 1909189 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": 1420650, "vin": [ { "gen": { "height": 1420640 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a96ef699147ba9a9d53012c9bf11f0103485539a6c98f96bab77b8512f33b4f0" } } ], "extra": [ 1, 163, 92, 44, 61, 109, 1, 185, 49, 112, 211, 19, 72, 11, 190, 207, 14, 81, 198, 49, 246, 242, 238, 14, 167, 103, 241, 48, 232, 204, 134, 13, 0, 2, 17, 0, 0, 0, 1, 78, 123, 252, 9, 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