Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f1b3c36f041f538cde386152ba6baa9368c9aedf96970e7e50c2cee1459f3740

Tx prefix hash: 443e44f608c39ac077e5d7e90a0b346daffc36e5ed879c26cc842f4cc8bc8e47
Tx public key: 4e485087c4e52c4a9e9e45216e853ea36287747e092c2e0f513c06161029edc8
Timestamp: 1614504930 Timestamp [UCT]: 2021-02-28 09:35:30 Age [y:d:h:m:s]: 03:304:20:21:07
Block: 208358 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 977166 RingCT/type: yes/0
Extra: 014e485087c4e52c4a9e9e45216e853ea36287747e092c2e0f513c06161029edc80211000003b0f1e90b67000000000000000000

1 output(s) for total of 125.211399364000 dcy

stealth address amount amount idx
00: 144f25a751bea32df2589fd423f0d82b43eca30e98af88d28798158757c0e00d 125.211399364000 425041 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": 208368, "vin": [ { "gen": { "height": 208358 } } ], "vout": [ { "amount": 125211399364, "target": { "key": "144f25a751bea32df2589fd423f0d82b43eca30e98af88d28798158757c0e00d" } } ], "extra": [ 1, 78, 72, 80, 135, 196, 229, 44, 74, 158, 158, 69, 33, 110, 133, 62, 163, 98, 135, 116, 126, 9, 44, 46, 15, 81, 60, 6, 22, 16, 41, 237, 200, 2, 17, 0, 0, 3, 176, 241, 233, 11, 103, 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