Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d338af638df6cd617abdd7b0b7604a79984e6b59441c9a55b52616d6836763e7

Tx prefix hash: 99d747fb3435b414d891cb237d9f93923173402811a6b987ab1bc2efc938d8b7
Tx public key: 381464e1be90acc84729815e4a64cb042e3dbb13cfcb1d38682045cb1bc65946
Timestamp: 1713530880 Timestamp [UCT]: 2024-04-19 12:48:00 Age [y:d:h:m:s]: 00:253:03:54:50
Block: 1003919 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 181215 RingCT/type: yes/0
Extra: 01381464e1be90acc84729815e4a64cb042e3dbb13cfcb1d38682045cb1bc6594602110000000859dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b3bdb86647120f5ec4821bab49aa98e332a26cc2a11d8a2a8cf1481ed1b40d48 0.600000000000 1464469 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": 1003929, "vin": [ { "gen": { "height": 1003919 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b3bdb86647120f5ec4821bab49aa98e332a26cc2a11d8a2a8cf1481ed1b40d48" } } ], "extra": [ 1, 56, 20, 100, 225, 190, 144, 172, 200, 71, 41, 129, 94, 74, 100, 203, 4, 46, 61, 187, 19, 207, 203, 29, 56, 104, 32, 69, 203, 27, 198, 89, 70, 2, 17, 0, 0, 0, 8, 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