Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: dcaa61e8cee3c17879320c5b76f3dfc713d0162b063c54cd5d532a4dc89e4c0f

Tx prefix hash: dcd9b56c63390690c3f5df301b61eeda9ae4047dc6e9572405148ec1fea26d45
Tx public key: e849eed9347a3c9cdd00f2e13366818027b55d77299d1a6ec64e315a2518ba14
Timestamp: 1676970562 Timestamp [UCT]: 2023-02-21 09:09:22 Age [y:d:h:m:s]: 02:053:16:24:44
Block: 701700 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 559965 RingCT/type: yes/0
Extra: 01e849eed9347a3c9cdd00f2e13366818027b55d77299d1a6ec64e315a2518ba1402110000000333af99f4000000000000000000

1 output(s) for total of 2.903865662000 dcy

stealth address amount amount idx
00: 8170d612acef15ac1775c80f9a19b170bcaacb7e149a1d868067c3aa956644ee 2.903865662000 1145189 of 0

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": 701710, "vin": [ { "gen": { "height": 701700 } } ], "vout": [ { "amount": 2903865662, "target": { "key": "8170d612acef15ac1775c80f9a19b170bcaacb7e149a1d868067c3aa956644ee" } } ], "extra": [ 1, 232, 73, 238, 217, 52, 122, 60, 156, 221, 0, 242, 225, 51, 102, 129, 128, 39, 181, 93, 119, 41, 157, 26, 110, 198, 78, 49, 90, 37, 24, 186, 20, 2, 17, 0, 0, 0, 3, 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