Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a4277e1111bfcf76e9a317cf2a790dd80fc7ec11badbedb3719a02c3d0231f8a

Tx prefix hash: 9f6510de116eb144ed4bb1f0147c9d195684e061485ccd04f7a4920c5ec6e8d6
Tx public key: 1adfa13517f5ec32c0d124e60c24b0fed2d0a25c0949a7b8a57a228e1be3488b
Timestamp: 1742158922 Timestamp [UCT]: 2025-03-16 21:02:02 Age [y:d:h:m:s]: 00:290:23:08:04
Block: 1240809 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 205736 RingCT/type: yes/0
Extra: 011adfa13517f5ec32c0d124e60c24b0fed2d0a25c0949a7b8a57a228e1be3488b0211000000021f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b351890c424b7f3d908fea0c3c6cbddea45f7c4a780d5ad6ace0e75817c6f65d 0.600000000000 1727782 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": 1240819, "vin": [ { "gen": { "height": 1240809 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b351890c424b7f3d908fea0c3c6cbddea45f7c4a780d5ad6ace0e75817c6f65d" } } ], "extra": [ 1, 26, 223, 161, 53, 23, 245, 236, 50, 192, 209, 36, 230, 12, 36, 176, 254, 210, 208, 162, 92, 9, 73, 167, 184, 165, 122, 34, 142, 27, 227, 72, 139, 2, 17, 0, 0, 0, 2, 31, 10, 83, 235, 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