Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 8c98780eb9beb419b05d7a953d4d30b3c3a5e214afb4ecff6b1e7890be529af1

Tx prefix hash: ff023e8bc66c78af74d72703bf3be96d9527d7f25738fd14a6f4f534fa4e5ac8
Tx public key: b41776a9c157519fb6e2ec99ce1fc889e8d2229059b76bdce967d4406aff6d32
Timestamp: 1736758140 Timestamp [UCT]: 2025-01-13 08:49:00 Age [y:d:h:m:s]: 00:071:02:24:10
Block: 1196349 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 50586 RingCT/type: yes/0
Extra: 01b41776a9c157519fb6e2ec99ce1fc889e8d2229059b76bdce967d4406aff6d32021100000001007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e79e61877ef4a1727d4c43c1bad43e216fc68e3511bf755a707fbb1c532f32ec 0.600000000000 1682948 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": 1196359, "vin": [ { "gen": { "height": 1196349 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e79e61877ef4a1727d4c43c1bad43e216fc68e3511bf755a707fbb1c532f32ec" } } ], "extra": [ 1, 180, 23, 118, 169, 193, 87, 81, 159, 182, 226, 236, 153, 206, 31, 200, 137, 232, 210, 34, 144, 89, 183, 107, 220, 233, 103, 212, 64, 106, 255, 109, 50, 2, 17, 0, 0, 0, 1, 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