Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 5e2eca7db4b509dc91fddf75123ea97248f6e3e444804d3ff189a4071926db62

Tx prefix hash: 1837d6de0aa8fbb471a7ab5a37413167ee296e3ead44a1be79c263928fe79d8c
Tx public key: 2eb07ea358f63256da82a9ae2b18e6ce1b66b18d4e4c9cee29be349870543f74
Timestamp: 1720374290 Timestamp [UCT]: 2024-07-07 17:44:50 Age [y:d:h:m:s]: 00:302:00:52:12
Block: 1060651 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 215828 RingCT/type: yes/0
Extra: 012eb07ea358f63256da82a9ae2b18e6ce1b66b18d4e4c9cee29be349870543f74021100000005e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 40a7d5e584e4775c044f7874ba5f55914dc68e2b4c0e5502acd1eb597056c47c 0.600000000000 1531136 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": 1060661, "vin": [ { "gen": { "height": 1060651 } } ], "vout": [ { "amount": 600000000, "target": { "key": "40a7d5e584e4775c044f7874ba5f55914dc68e2b4c0e5502acd1eb597056c47c" } } ], "extra": [ 1, 46, 176, 126, 163, 88, 246, 50, 86, 218, 130, 169, 174, 43, 24, 230, 206, 27, 102, 177, 141, 78, 76, 156, 238, 41, 190, 52, 152, 112, 84, 63, 116, 2, 17, 0, 0, 0, 5, 233, 20, 221, 21, 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