Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 7ef54f504afe52dfd388b9347ca3792a6bdfe63ebce664311fade3d37c56e373

Tx prefix hash: d017159e985f18c7c38a326d5a7ef1098ece9c9cc0bc919c84cef27e5f97d882
Tx public key: 4dc327cdb2f93d6bdfb4e81048730f0586f52d0115aeaff7e4ef14e353616859
Timestamp: 1728802529 Timestamp [UCT]: 2024-10-13 06:55:29 Age [y:d:h:m:s]: 01:026:12:46:27
Block: 1130537 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 277327 RingCT/type: yes/0
Extra: 014dc327cdb2f93d6bdfb4e81048730f0586f52d0115aeaff7e4ef14e35361685902110000000391e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 875663dd6fa8a186a5112ada6171bdb23db7be2bfeca66ffada880aa306ba417 0.600000000000 1613414 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": 1130547, "vin": [ { "gen": { "height": 1130537 } } ], "vout": [ { "amount": 600000000, "target": { "key": "875663dd6fa8a186a5112ada6171bdb23db7be2bfeca66ffada880aa306ba417" } } ], "extra": [ 1, 77, 195, 39, 205, 178, 249, 61, 107, 223, 180, 232, 16, 72, 115, 15, 5, 134, 245, 45, 1, 21, 174, 175, 247, 228, 239, 20, 227, 83, 97, 104, 89, 2, 17, 0, 0, 0, 3, 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