Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a0ca795e9e5f087dc3ba6838dbd0bcc6e87b3bce6db06413554cc1e6eebed68c

Tx prefix hash: b384ea3691aabe791607bdcf4fe8071e24b8256dcd6a8a19fbc80f862e63a410
Tx public key: c5c426f9fa25f1e896599c8beea7d2de49d8fe06f11648ce4899909ac945b1f7
Timestamp: 1709306284 Timestamp [UCT]: 2024-03-01 15:18:04 Age [y:d:h:m:s]: 00:334:14:18:04
Block: 968908 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 239234 RingCT/type: yes/0
Extra: 01c5c426f9fa25f1e896599c8beea7d2de49d8fe06f11648ce4899909ac945b1f70211000000087a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 0fe4594ba31d9ed9ad7e51ffedde53e7d551cecc40ccc130845fdab1871d471f 0.600000000000 1428735 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": 968918, "vin": [ { "gen": { "height": 968908 } } ], "vout": [ { "amount": 600000000, "target": { "key": "0fe4594ba31d9ed9ad7e51ffedde53e7d551cecc40ccc130845fdab1871d471f" } } ], "extra": [ 1, 197, 196, 38, 249, 250, 37, 241, 232, 150, 89, 156, 139, 238, 167, 210, 222, 73, 216, 254, 6, 241, 22, 72, 206, 72, 153, 144, 154, 201, 69, 177, 247, 2, 17, 0, 0, 0, 8, 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