Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2e206b7822a01824ddaf6646d28bccb7fa1fe7296f7e6accf7ca2642af26260d

Tx prefix hash: d44519da94c6a1e4d1e315e6e15b533cefa88222bbe0d8481c73605d18099982
Tx public key: f8845ece041a7e15fcc225d4c7d30f439390b1a1b6b537d9075d5843e37308da
Timestamp: 1737753792 Timestamp [UCT]: 2025-01-24 21:23:12 Age [y:d:h:m:s]: 00:144:04:33:25
Block: 1204537 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 102799 RingCT/type: yes/0
Extra: 01f8845ece041a7e15fcc225d4c7d30f439390b1a1b6b537d9075d5843e37308da0211000000021f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 13e302d6f943c755e4c41d422ac5c92344a0b636342a09805960e3e8f7b1b6c5 0.600000000000 1691224 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": 1204547, "vin": [ { "gen": { "height": 1204537 } } ], "vout": [ { "amount": 600000000, "target": { "key": "13e302d6f943c755e4c41d422ac5c92344a0b636342a09805960e3e8f7b1b6c5" } } ], "extra": [ 1, 248, 132, 94, 206, 4, 26, 126, 21, 252, 194, 37, 212, 199, 211, 15, 67, 147, 144, 177, 161, 182, 181, 55, 217, 7, 93, 88, 67, 227, 115, 8, 218, 2, 17, 0, 0, 0, 2, 31, 10, 83, 235, 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