Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d402f1be3ccb13581e09825bbe9bc85b7c1a5dd88875e78424b5c4c0ac15e804

Tx prefix hash: 3962c9487ba4132d2206b02ab31b30040ba9f0b0a5eb427a4568c7e18bc06b1d
Tx public key: 3a498f9b99b7f85f3dd2ba3311f642f0f3c7ce816e839f0b91a3e7bdfe014e50
Timestamp: 1703360974 Timestamp [UCT]: 2023-12-23 19:49:34 Age [y:d:h:m:s]: 02:039:21:08:46
Block: 919607 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 548142 RingCT/type: yes/0
Extra: 013a498f9b99b7f85f3dd2ba3311f642f0f3c7ce816e839f0b91a3e7bdfe014e5002110000000352d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 34ba3496003e209b544eadcd4ce14985118d3d5abb4fb5d8ead82ab2612c4f2e 0.600000000000 1377283 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": 919617, "vin": [ { "gen": { "height": 919607 } } ], "vout": [ { "amount": 600000000, "target": { "key": "34ba3496003e209b544eadcd4ce14985118d3d5abb4fb5d8ead82ab2612c4f2e" } } ], "extra": [ 1, 58, 73, 143, 155, 153, 183, 248, 95, 61, 210, 186, 51, 17, 246, 66, 240, 243, 199, 206, 129, 110, 131, 159, 11, 145, 163, 231, 189, 254, 1, 78, 80, 2, 17, 0, 0, 0, 3, 82, 212, 126, 148, 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