Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0cc784d3e41e241016f82a282a12e9d56e28b783dd546e19747cac166ccf7715

Tx prefix hash: 153ec03f2ef79093a2e7f8df1c34b066c7fbeb404c2fdd18fbdd481c59fe29b0
Tx public key: 57ce37c00e494231a2775025f8f0912fb3231d591617f43a45d97d66a0c602e7
Timestamp: 1725651255 Timestamp [UCT]: 2024-09-06 19:34:15 Age [y:d:h:m:s]: 00:215:07:02:29
Block: 1104408 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 153718 RingCT/type: yes/0
Extra: 0157ce37c00e494231a2775025f8f0912fb3231d591617f43a45d97d66a0c602e702110000000191e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 68153807e559b70118b6cffa2fa37c0a6aa6b009b08163d8cd5e88a4274bee92 0.600000000000 1581537 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": 1104418, "vin": [ { "gen": { "height": 1104408 } } ], "vout": [ { "amount": 600000000, "target": { "key": "68153807e559b70118b6cffa2fa37c0a6aa6b009b08163d8cd5e88a4274bee92" } } ], "extra": [ 1, 87, 206, 55, 192, 14, 73, 66, 49, 162, 119, 80, 37, 248, 240, 145, 47, 179, 35, 29, 89, 22, 23, 244, 58, 69, 217, 125, 102, 160, 198, 2, 231, 2, 17, 0, 0, 0, 1, 145, 225, 60, 4, 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