Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 35a2b9d5cb7ac0cc81dd5f05000111d2f35c3374e3471d2ecfce20d77e01aa36

Tx prefix hash: 321a028c2717a8160333815154b368643da056ba22fd1e87fc35a028ab4166f9
Tx public key: 39aadff9f3a158dbf97829dc25bbe8202ed26211eefeee4b9cda6ae2b9ff828e
Timestamp: 1737416215 Timestamp [UCT]: 2025-01-20 23:36:55 Age [y:d:h:m:s]: 00:304:00:46:02
Block: 1201751 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 214829 RingCT/type: yes/0
Extra: 0139aadff9f3a158dbf97829dc25bbe8202ed26211eefeee4b9cda6ae2b9ff828e0211000000041f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: c11d2dff01363699575c803bbc73ef47de058d294fb4a10b723141171b89e3e0 0.600000000000 1688408 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": 1201761, "vin": [ { "gen": { "height": 1201751 } } ], "vout": [ { "amount": 600000000, "target": { "key": "c11d2dff01363699575c803bbc73ef47de058d294fb4a10b723141171b89e3e0" } } ], "extra": [ 1, 57, 170, 223, 249, 243, 161, 88, 219, 249, 120, 41, 220, 37, 187, 232, 32, 46, 210, 98, 17, 238, 254, 238, 75, 156, 218, 106, 226, 185, 255, 130, 142, 2, 17, 0, 0, 0, 4, 31, 10, 83, 235, 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