Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f09057de5b4c6e30cbee9dcf72af6de98c7c56d799013c802e2479627a8f14b6

Tx prefix hash: 8fe4dbc6913c08dabef9833d2f819f766f00b021d7c1ed6f59c7b6e52ca459e1
Tx public key: 32ad440b5bbeadf44b64c31553adf3d21cc2ef75ab82eecf8892b776874cef98
Timestamp: 1718490416 Timestamp [UCT]: 2024-06-15 22:26:56 Age [y:d:h:m:s]: 00:253:22:01:23
Block: 1045062 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 181395 RingCT/type: yes/0
Extra: 0132ad440b5bbeadf44b64c31553adf3d21cc2ef75ab82eecf8892b776874cef9802110000000e7a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 691e164185227eaa48b3af5df41891b2301a10a41343e7f7349ceb5b708d2a3a 0.600000000000 1514535 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": 1045072, "vin": [ { "gen": { "height": 1045062 } } ], "vout": [ { "amount": 600000000, "target": { "key": "691e164185227eaa48b3af5df41891b2301a10a41343e7f7349ceb5b708d2a3a" } } ], "extra": [ 1, 50, 173, 68, 11, 91, 190, 173, 244, 75, 100, 195, 21, 83, 173, 243, 210, 28, 194, 239, 117, 171, 130, 238, 207, 136, 146, 183, 118, 135, 76, 239, 152, 2, 17, 0, 0, 0, 14, 122, 156, 244, 199, 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