Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 14a52e17e5e4de3fa2891047034c1df4f1989dc835ffcac44507927d4a9bf70a

Tx prefix hash: f81ba7899cb016d6a75354d3c26b39a754cc05125bd4bcac2893718a8bd96eb1
Tx public key: 1d4eac5852b5dd46e76a3c7c918fd3edacfd65ca0dde7e1703c9a579c060cf82
Timestamp: 1721255522 Timestamp [UCT]: 2024-07-17 22:32:02 Age [y:d:h:m:s]: 00:251:07:53:21
Block: 1067978 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 179513 RingCT/type: yes/0
Extra: 011d4eac5852b5dd46e76a3c7c918fd3edacfd65ca0dde7e1703c9a579c060cf8202110000002191e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 803c5340441f5f4ead033bf50f874849ca25c72938ccbd8a5d03259cc73e13b3 0.600000000000 1538943 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": 1067988, "vin": [ { "gen": { "height": 1067978 } } ], "vout": [ { "amount": 600000000, "target": { "key": "803c5340441f5f4ead033bf50f874849ca25c72938ccbd8a5d03259cc73e13b3" } } ], "extra": [ 1, 29, 78, 172, 88, 82, 181, 221, 70, 231, 106, 60, 124, 145, 143, 211, 237, 172, 253, 101, 202, 13, 222, 126, 23, 3, 201, 165, 121, 192, 96, 207, 130, 2, 17, 0, 0, 0, 33, 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