Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 475d675d6b7fc1bf0188871a32c4c98d5eac1b006b26ce2766d95369d582362b

Tx prefix hash: 33d7a129ffe826f72be48bdf32ace94540588756185a23a0b1ca55b249f81769
Tx public key: 5239e7d1a2508f00e7adcc2db65e6b3394d55d5f9d511936a157dbf8d561a3b7
Timestamp: 1738007822 Timestamp [UCT]: 2025-01-27 19:57:02 Age [y:d:h:m:s]: 00:140:22:26:23
Block: 1206441 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 100673 RingCT/type: yes/0
Extra: 015239e7d1a2508f00e7adcc2db65e6b3394d55d5f9d511936a157dbf8d561a3b702110000000325a35a0f000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 754ea7cfd4798f9d2c9e45cbc545c206404454f8701b4090bf8b75f804274a98 0.600000000000 1693146 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": 1206451, "vin": [ { "gen": { "height": 1206441 } } ], "vout": [ { "amount": 600000000, "target": { "key": "754ea7cfd4798f9d2c9e45cbc545c206404454f8701b4090bf8b75f804274a98" } } ], "extra": [ 1, 82, 57, 231, 209, 162, 80, 143, 0, 231, 173, 204, 45, 182, 94, 107, 51, 148, 213, 93, 95, 157, 81, 25, 54, 161, 87, 219, 248, 213, 97, 163, 183, 2, 17, 0, 0, 0, 3, 37, 163, 90, 15, 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