Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0e94032cfcaa2f988423e4a5dbff9feb5c9dbd41d3b01e18f313f97229f09574

Tx prefix hash: 0bcc537491d3d7afefaca0dd67f975e4c78a4da28a3af92ffbe13bf46c87758d
Tx public key: 744227b9e8b09d90d84a5a5433e5be6cd11b67358ed24d66870f37ebfbaf1914
Timestamp: 1702040941 Timestamp [UCT]: 2023-12-08 13:09:01 Age [y:d:h:m:s]: 01:191:23:16:26
Block: 908655 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 398299 RingCT/type: yes/0
Extra: 01744227b9e8b09d90d84a5a5433e5be6cd11b67358ed24d66870f37ebfbaf191402110000000233af99f4000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 7803e0fbcfb1e7c218e0b3027b4757a6c5ceb85e010aa09c0f7dc87aa216665f 0.600000000000 1365700 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": 908665, "vin": [ { "gen": { "height": 908655 } } ], "vout": [ { "amount": 600000000, "target": { "key": "7803e0fbcfb1e7c218e0b3027b4757a6c5ceb85e010aa09c0f7dc87aa216665f" } } ], "extra": [ 1, 116, 66, 39, 185, 232, 176, 157, 144, 216, 74, 90, 84, 51, 229, 190, 108, 209, 27, 103, 53, 142, 210, 77, 102, 135, 15, 55, 235, 251, 175, 25, 20, 2, 17, 0, 0, 0, 2, 51, 175, 153, 244, 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