Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: fe1608dd4e9f6e39fdb9109162153da4159fdf15de7aa8d596f7f474d8ff3fd6

Tx prefix hash: 982d811b594703707529b8276882d8348c9c2c7fd29d62607f36a8bd6b412250
Tx public key: 25737ae7de4ab6ca4b9bc52a8651c266170fb2b88ed95b58d7d50b1bc589d9e9
Timestamp: 1703382030 Timestamp [UCT]: 2023-12-24 01:40:30 Age [y:d:h:m:s]: 01:125:21:56:12
Block: 919778 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 351140 RingCT/type: yes/0
Extra: 0125737ae7de4ab6ca4b9bc52a8651c266170fb2b88ed95b58d7d50b1bc589d9e902110000000359dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 9354c28d311fbbbd9fd9aaed4a6118c6376197f4f1fc1d4f18694a7f0662fed7 0.600000000000 1377456 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": 919788, "vin": [ { "gen": { "height": 919778 } } ], "vout": [ { "amount": 600000000, "target": { "key": "9354c28d311fbbbd9fd9aaed4a6118c6376197f4f1fc1d4f18694a7f0662fed7" } } ], "extra": [ 1, 37, 115, 122, 231, 222, 74, 182, 202, 75, 155, 197, 42, 134, 81, 194, 102, 23, 15, 178, 184, 142, 217, 91, 88, 215, 213, 11, 27, 197, 137, 217, 233, 2, 17, 0, 0, 0, 3, 89, 218, 211, 245, 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