Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e8b6406e04b0e83a742987d6f34ce2e22b620b3a5c6f382e4f7821ae802a8c75

Tx prefix hash: d4f0b3a22ed0f4de4de3997f655534d560da3ef07352fcb170fa001c21cf739d
Tx public key: 442c427bfeb326841590f0e63740c73b3aba0a616ffabafcaa120c19cfd3722c
Timestamp: 1715884401 Timestamp [UCT]: 2024-05-16 18:33:21 Age [y:d:h:m:s]: 00:341:00:03:36
Block: 1023436 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 243743 RingCT/type: yes/0
Extra: 01442c427bfeb326841590f0e63740c73b3aba0a616ffabafcaa120c19cfd3722c0211000000020011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 989270d6a5cdbebef4826b39102b7d8030ecad5e2e8e34a6c8dbfcccfb04c2dc 0.600000000000 1488411 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": 1023446, "vin": [ { "gen": { "height": 1023436 } } ], "vout": [ { "amount": 600000000, "target": { "key": "989270d6a5cdbebef4826b39102b7d8030ecad5e2e8e34a6c8dbfcccfb04c2dc" } } ], "extra": [ 1, 68, 44, 66, 123, 254, 179, 38, 132, 21, 144, 240, 230, 55, 64, 199, 59, 58, 186, 10, 97, 111, 250, 186, 252, 170, 18, 12, 25, 207, 211, 114, 44, 2, 17, 0, 0, 0, 2, 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