Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c7e05498072bc03520e6783e1fd70c6d557ba380df4e340dfb10366de49dc9c3

Tx prefix hash: bf272fc2a056a1e1c752b41312611e59f73b789b3047cddba4f9cbc84d5c97fa
Tx public key: eef80ee7ca0044ba16c0e1d337ed8c33435112f1d74564a711a31422511c964c
Timestamp: 1720977429 Timestamp [UCT]: 2024-07-14 17:17:09 Age [y:d:h:m:s]: 00:282:20:04:08
Block: 1065667 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 202068 RingCT/type: yes/0
Extra: 01eef80ee7ca0044ba16c0e1d337ed8c33435112f1d74564a711a31422511c964c02110000000191e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 43d922a9258e61d5352a5e61a309771bf3717f71906f4e1c6428d6b16b856723 0.600000000000 1536216 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": 1065677, "vin": [ { "gen": { "height": 1065667 } } ], "vout": [ { "amount": 600000000, "target": { "key": "43d922a9258e61d5352a5e61a309771bf3717f71906f4e1c6428d6b16b856723" } } ], "extra": [ 1, 238, 248, 14, 231, 202, 0, 68, 186, 22, 192, 225, 211, 55, 237, 140, 51, 67, 81, 18, 241, 215, 69, 100, 167, 17, 163, 20, 34, 81, 28, 150, 76, 2, 17, 0, 0, 0, 1, 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