Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ff5e15b0880c161d108f3c8ca91e4db1fa8be66223e47c53c8b5c61083e700f9

Tx prefix hash: 4a96b7024b82ead3171cf3809b53ef32d0d88f8421d3d45eff06218b8e54479a
Tx public key: 8149e86e5307c3da843d5ad94c195ebd26a0a5d0c1edbcad20329ea75876bbf2
Timestamp: 1713370999 Timestamp [UCT]: 2024-04-17 16:23:19 Age [y:d:h:m:s]: 01:023:08:53:05
Block: 1002596 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 277658 RingCT/type: yes/0
Extra: 018149e86e5307c3da843d5ad94c195ebd26a0a5d0c1edbcad20329ea75876bbf202110000000659dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a9d7f3b6b969a1bd0df71abf726848d85452b019947d55101e28e1ccf52131ee 0.600000000000 1463114 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": 1002606, "vin": [ { "gen": { "height": 1002596 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a9d7f3b6b969a1bd0df71abf726848d85452b019947d55101e28e1ccf52131ee" } } ], "extra": [ 1, 129, 73, 232, 110, 83, 7, 195, 218, 132, 61, 90, 217, 76, 25, 94, 189, 38, 160, 165, 208, 193, 237, 188, 173, 32, 50, 158, 167, 88, 118, 187, 242, 2, 17, 0, 0, 0, 6, 89, 218, 211, 245, 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