Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 808034a3eabc3a34a4dd95f8dbfb43280549e1c84bd480de0501daa00a4ef301

Tx prefix hash: e4f660d68e2e5f3c7f2451e16a9de2b066c70d38c45391c1a82582a0d039d97f
Tx public key: 503259b113734402e951c917a3afe3dbc49175ad893e7793ab38122bf6615e21
Timestamp: 1727072653 Timestamp [UCT]: 2024-09-23 06:24:13 Age [y:d:h:m:s]: 00:108:01:59:23
Block: 1116195 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 77273 RingCT/type: yes/0
Extra: 01503259b113734402e951c917a3afe3dbc49175ad893e7793ab38122bf6615e2102110000000191e13c04000000000000000000

1 output(s) for total of 0.608000000000 dcy

stealth address amount amount idx
00: 46aed056644bc3db0e1fb2c516bfeaf99ca89cd0ce7d41c50f3469cb60b6617f 0.608000000000 1596590 of 0

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": 1116205, "vin": [ { "gen": { "height": 1116195 } } ], "vout": [ { "amount": 608000000, "target": { "key": "46aed056644bc3db0e1fb2c516bfeaf99ca89cd0ce7d41c50f3469cb60b6617f" } } ], "extra": [ 1, 80, 50, 89, 177, 19, 115, 68, 2, 233, 81, 201, 23, 163, 175, 227, 219, 196, 145, 117, 173, 137, 62, 119, 147, 171, 56, 18, 43, 246, 97, 94, 33, 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