Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2006cdb30c0a668f039ca0b804cf8859ef2b029e88cf44fb1a2eba0f03dbed5d

Tx prefix hash: f08a5ae5b3a89bfaf8910d1215dda80ef312ff7e35eba13f37d35e3cb53c2e40
Tx public key: 843f6ca1c16e2132aef7edfbd0526db11d06f1bb90b689fd5081d754549a378d
Timestamp: 1576387709 Timestamp [UCT]: 2019-12-15 05:28:29 Age [y:d:h:m:s]: 05:015:21:03:40
Block: 27143 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1158288 RingCT/type: yes/0
Extra: 01843f6ca1c16e2132aef7edfbd0526db11d06f1bb90b689fd5081d754549a378d0211000000264ac5aa02000000000000000000

1 output(s) for total of 498.967586141000 dcy

stealth address amount amount idx
00: 529602f40985340e926f9438516d01c627b70cee9e60537aba59355f7c535cf9 498.967586141000 45008 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": 27153, "vin": [ { "gen": { "height": 27143 } } ], "vout": [ { "amount": 498967586141, "target": { "key": "529602f40985340e926f9438516d01c627b70cee9e60537aba59355f7c535cf9" } } ], "extra": [ 1, 132, 63, 108, 161, 193, 110, 33, 50, 174, 247, 237, 251, 208, 82, 109, 177, 29, 6, 241, 187, 144, 182, 137, 253, 80, 129, 215, 84, 84, 154, 55, 141, 2, 17, 0, 0, 0, 38, 74, 197, 170, 2, 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