Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0bb4d0a42148a5b3ae23b36da8eb50b23dbb0e88eee3602d20af7b7080383576

Tx prefix hash: 863e863547afeeae2c3c9628b767ff3956852a1567cebdda1e4b91c8576d863a
Tx public key: dc351c75e729c982a63d4d435174947e2a1c9664f90ff42aa1831cfe2d1b6623
Timestamp: 1763050856 Timestamp [UCT]: 2025-11-13 16:20:56 Age [y:d:h:m:s]: 00:040:09:35:10
Block: 1411341 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 28921 RingCT/type: yes/0
Extra: 01dc351c75e729c982a63d4d435174947e2a1c9664f90ff42aa1831cfe2d1b6623021100000005dfc3ba49000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 66dc5f90a5b98b09ab5a392365b613ab871075d2b89431366087c9f884781ebf 0.600000000000 1899802 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": 1411351, "vin": [ { "gen": { "height": 1411341 } } ], "vout": [ { "amount": 600000000, "target": { "key": "66dc5f90a5b98b09ab5a392365b613ab871075d2b89431366087c9f884781ebf" } } ], "extra": [ 1, 220, 53, 28, 117, 231, 41, 201, 130, 166, 61, 77, 67, 81, 116, 148, 126, 42, 28, 150, 100, 249, 15, 244, 42, 161, 131, 28, 254, 45, 27, 102, 35, 2, 17, 0, 0, 0, 5, 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