Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 7de6c5c428c4a32d651e4f396094df4dbf1e924bfa5ac90072a9d8b443ff1f50

Tx prefix hash: 2ed7506a5dde969eefae7ede4d66f228d9f6438e37f373a877b18b0cd289f51c
Tx public key: a30655ff2cc3e8efda9f5c66d0ce04e21eaab0e3dd08ab42c1c34fcc7a772232
Timestamp: 1706501560 Timestamp [UCT]: 2024-01-29 04:12:40 Age [y:d:h:m:s]: 01:079:22:00:06
Block: 945624 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 318202 RingCT/type: yes/0
Extra: 01a30655ff2cc3e8efda9f5c66d0ce04e21eaab0e3dd08ab42c1c34fcc7a7722320211000000010011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 41400d91a145e096ecc89ee8007fe0c905d306ce0ab62f3fdd39b87e567731e4 0.600000000000 1403940 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": 945634, "vin": [ { "gen": { "height": 945624 } } ], "vout": [ { "amount": 600000000, "target": { "key": "41400d91a145e096ecc89ee8007fe0c905d306ce0ab62f3fdd39b87e567731e4" } } ], "extra": [ 1, 163, 6, 85, 255, 44, 195, 232, 239, 218, 159, 92, 102, 208, 206, 4, 226, 30, 170, 176, 227, 221, 8, 171, 66, 193, 195, 79, 204, 122, 119, 34, 50, 2, 17, 0, 0, 0, 1, 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