Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 5256b3e37e2793d55608e51e0846048f99ad6a1a6a4c45bcb056439ed30c5bc1

Tx prefix hash: 2102cc8f6f48aed712e3c07784385716ca56d78d83b4173e68f4e5b80bbbe84f
Tx public key: 80aae365d63ff5f09a303f9d0d7e8f2f3965139ba9ddc53e70ea798aeb67aa2c
Timestamp: 1705201807 Timestamp [UCT]: 2024-01-14 03:10:07 Age [y:d:h:m:s]: 01:322:13:40:08
Block: 934844 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 489402 RingCT/type: yes/0
Extra: 0180aae365d63ff5f09a303f9d0d7e8f2f3965139ba9ddc53e70ea798aeb67aa2c02110000000452d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: c3f0f729066382b0dbca0d0eabf5ffbddff0cf21ec99e3d742446dbbd25f962c 0.600000000000 1392860 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": 934854, "vin": [ { "gen": { "height": 934844 } } ], "vout": [ { "amount": 600000000, "target": { "key": "c3f0f729066382b0dbca0d0eabf5ffbddff0cf21ec99e3d742446dbbd25f962c" } } ], "extra": [ 1, 128, 170, 227, 101, 214, 63, 245, 240, 154, 48, 63, 157, 13, 126, 143, 47, 57, 101, 19, 155, 169, 221, 197, 62, 112, 234, 121, 138, 235, 103, 170, 44, 2, 17, 0, 0, 0, 4, 82, 212, 126, 148, 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