Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 401e9f2bf4199a98003e6f8c3575df09cff353c887b465664183a476aa34a7b7

Tx prefix hash: af3ffe3cb05306ef2c5789ad6ab74b510c4d567ee4c0b3b23672cdac0896cea4
Tx public key: 579a11ae9790627a381b8d3357e4bb1ad20b90d7e4df6ccc05123ae77f8c3c7b
Timestamp: 1726092019 Timestamp [UCT]: 2024-09-11 22:00:19 Age [y:d:h:m:s]: 00:107:03:51:14
Block: 1108061 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 76625 RingCT/type: yes/0
Extra: 01579a11ae9790627a381b8d3357e4bb1ad20b90d7e4df6ccc05123ae77f8c3c7b02110000000491e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 9bfffdd7fe89a38aaee722ff95e675ffecd77408a716040e75502bf957b8d3df 0.600000000000 1585822 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": 1108071, "vin": [ { "gen": { "height": 1108061 } } ], "vout": [ { "amount": 600000000, "target": { "key": "9bfffdd7fe89a38aaee722ff95e675ffecd77408a716040e75502bf957b8d3df" } } ], "extra": [ 1, 87, 154, 17, 174, 151, 144, 98, 122, 56, 27, 141, 51, 87, 228, 187, 26, 210, 11, 144, 215, 228, 223, 108, 204, 5, 18, 58, 231, 127, 140, 60, 123, 2, 17, 0, 0, 0, 4, 145, 225, 60, 4, 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