Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 7fed5c6614eb6d7940a8def7069772d043790b35ec409a0859a31b1d627cc69b

Tx prefix hash: 618127591e4748b82733133073de53f2ed22181af3f913315675714a3016797d
Tx public key: aa9360aea29f2594e2a5055d4df800ba0b1aae2c903b28d9a8844734e1c6ea11
Timestamp: 1709100886 Timestamp [UCT]: 2024-02-28 06:14:46 Age [y:d:h:m:s]: 01:050:08:32:44
Block: 967201 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 297011 RingCT/type: yes/0
Extra: 01aa9360aea29f2594e2a5055d4df800ba0b1aae2c903b28d9a8844734e1c6ea110211000000047a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 6df90da86d59a2b91f0563f0d41106a980edf354f0adb4f2fc96df262e78773e 0.600000000000 1426972 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": 967211, "vin": [ { "gen": { "height": 967201 } } ], "vout": [ { "amount": 600000000, "target": { "key": "6df90da86d59a2b91f0563f0d41106a980edf354f0adb4f2fc96df262e78773e" } } ], "extra": [ 1, 170, 147, 96, 174, 162, 159, 37, 148, 226, 165, 5, 93, 77, 248, 0, 186, 11, 26, 174, 44, 144, 59, 40, 217, 168, 132, 71, 52, 225, 198, 234, 17, 2, 17, 0, 0, 0, 4, 122, 156, 244, 199, 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