Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: fcdd8c949615f2aaa622d6059b57db3eb4c8d958198fcf64296add1ca552b9af

Tx prefix hash: 3428f64e9e0767011ba0f4f875f07dd0040c3fdc07e7a500e206e214eaa85eff
Tx public key: e43429f208673e8ee5274b0cd1b90655e6c451439f74a4232c55a7164f87f7d1
Timestamp: 1699357413 Timestamp [UCT]: 2023-11-07 11:43:33 Age [y:d:h:m:s]: 01:221:11:10:07
Block: 886425 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 419410 RingCT/type: yes/0
Extra: 01e43429f208673e8ee5274b0cd1b90655e6c451439f74a4232c55a7164f87f7d102110000000875e3f0e9000000000000000000

1 output(s) for total of 0.709424211000 dcy

stealth address amount amount idx
00: 48c70dbeefeef9453ed1952226e1f5e38ce5fe6855d6428fbf6f458695218804 0.709424211000 1342242 of 0

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": 886435, "vin": [ { "gen": { "height": 886425 } } ], "vout": [ { "amount": 709424211, "target": { "key": "48c70dbeefeef9453ed1952226e1f5e38ce5fe6855d6428fbf6f458695218804" } } ], "extra": [ 1, 228, 52, 41, 242, 8, 103, 62, 142, 229, 39, 75, 12, 209, 185, 6, 85, 230, 196, 81, 67, 159, 116, 164, 35, 44, 85, 167, 22, 79, 135, 247, 209, 2, 17, 0, 0, 0, 8, 117, 227, 240, 233, 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