Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 7df8e152dfc5e8b8a58e1b8c453e6d86ce3b320551c6604dfc8b4c320e8006a0

Tx prefix hash: a552d81de10bc4c47d4152742f556f8f708ec5eadbb13314cda9cfa1123c2542
Tx public key: 4e6ffbf04b8e9a99a9abd011a2a3faecf478e200ae426d445304464b1160b4b8
Timestamp: 1715662793 Timestamp [UCT]: 2024-05-14 04:59:53 Age [y:d:h:m:s]: 00:323:21:40:01
Block: 1021601 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 231506 RingCT/type: yes/0
Extra: 014e6ffbf04b8e9a99a9abd011a2a3faecf478e200ae426d445304464b1160b4b80211000000060011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 16d20a2db717638ba3cdcf3822da13ef9f98be6fdc6559f9bc9f7b103ed83568 0.600000000000 1485966 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": 1021611, "vin": [ { "gen": { "height": 1021601 } } ], "vout": [ { "amount": 600000000, "target": { "key": "16d20a2db717638ba3cdcf3822da13ef9f98be6fdc6559f9bc9f7b103ed83568" } } ], "extra": [ 1, 78, 111, 251, 240, 75, 142, 154, 153, 169, 171, 208, 17, 162, 163, 250, 236, 244, 120, 226, 0, 174, 66, 109, 68, 83, 4, 70, 75, 17, 96, 180, 184, 2, 17, 0, 0, 0, 6, 0, 17, 5, 91, 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