Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e28da216e756b27bce4cbd31e9a39c65ea97f7ab62eabb868907a31288beb050

Tx prefix hash: f1bdc931a08f28d80b05de05ffad02717947d43240fc8ea7ff3820a42ac192b7
Tx public key: 0ef53e216ee7ff0e8ecb34427543356074c939ec6d9e17db5b464221e6805b2b
Timestamp: 1735846914 Timestamp [UCT]: 2025-01-02 19:41:54 Age [y:d:h:m:s]: 00:098:13:00:41
Block: 1188801 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 70219 RingCT/type: yes/0
Extra: 010ef53e216ee7ff0e8ecb34427543356074c939ec6d9e17db5b464221e6805b2b021100000002007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 7ca532d85cf95f8fc21a8aee575bd4455b1d03e20b5d891c318cf4532d9f33d5 0.600000000000 1675304 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": 1188811, "vin": [ { "gen": { "height": 1188801 } } ], "vout": [ { "amount": 600000000, "target": { "key": "7ca532d85cf95f8fc21a8aee575bd4455b1d03e20b5d891c318cf4532d9f33d5" } } ], "extra": [ 1, 14, 245, 62, 33, 110, 231, 255, 14, 142, 203, 52, 66, 117, 67, 53, 96, 116, 201, 57, 236, 109, 158, 23, 219, 91, 70, 66, 33, 230, 128, 91, 43, 2, 17, 0, 0, 0, 2, 0, 127, 151, 138, 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