Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a5c9a6bb551e488c4236fdf1c9bb636e42918400e31ad633f3e35bb942a8b06c

Tx prefix hash: 259cc06c45b49c98d6dcb8d6ad1fb47a5fe4962231937ae6ac3c81650631170e
Tx public key: 03f0ef6549e75acc391222cbee1cd7dd123b09988f1e17dbe4ee0906afe94a5e
Timestamp: 1718661197 Timestamp [UCT]: 2024-06-17 21:53:17 Age [y:d:h:m:s]: 01:168:00:48:33
Block: 1046453 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 378688 RingCT/type: yes/0
Extra: 0103f0ef6549e75acc391222cbee1cd7dd123b09988f1e17dbe4ee0906afe94a5e02110000000259dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f85e92eeec180a10d9dfca769c7b03347583ce860df15ec8c9a3b048085be204 0.600000000000 1516266 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": 1046463, "vin": [ { "gen": { "height": 1046453 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f85e92eeec180a10d9dfca769c7b03347583ce860df15ec8c9a3b048085be204" } } ], "extra": [ 1, 3, 240, 239, 101, 73, 231, 90, 204, 57, 18, 34, 203, 238, 28, 215, 221, 18, 59, 9, 152, 143, 30, 23, 219, 228, 238, 9, 6, 175, 233, 74, 94, 2, 17, 0, 0, 0, 2, 89, 218, 211, 245, 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