Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 989eac959bf83e4b44308520b9bee601b018eff9e3bbe81a3a271af2e0c4008b

Tx prefix hash: 71697076568a8561fb618698026623675bf0f4988d5ab5c38c1c288f2ad08fcc
Tx public key: 3a7919aa2e5d4fbc0e971851d13a1314bb0bf9ee221e6c10010a82c4557a1bab
Timestamp: 1763908165 Timestamp [UCT]: 2025-11-23 14:29:25 Age [y:d:h:m:s]: 00:004:04:09:10
Block: 1418447 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 2995 RingCT/type: yes/0
Extra: 013a7919aa2e5d4fbc0e971851d13a1314bb0bf9ee221e6c10010a82c4557a1bab021100000009d6e19d7c000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: af1c383a2dbf58da40752a5874f33b57a81f6bc458f2ef740f7a7469814ecd0d 0.600000000000 1906978 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": 1418457, "vin": [ { "gen": { "height": 1418447 } } ], "vout": [ { "amount": 600000000, "target": { "key": "af1c383a2dbf58da40752a5874f33b57a81f6bc458f2ef740f7a7469814ecd0d" } } ], "extra": [ 1, 58, 121, 25, 170, 46, 93, 79, 188, 14, 151, 24, 81, 209, 58, 19, 20, 187, 11, 249, 238, 34, 30, 108, 16, 1, 10, 130, 196, 85, 122, 27, 171, 2, 17, 0, 0, 0, 9, 214, 225, 157, 124, 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