Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2555e05d1ff79eba093d3b04b7e4457d1e894e1006515854f61501e35817110d

Tx prefix hash: f53d33877a3a2719461b075ce5d4df4f890225a68b5230f9b77802fe9615c986
Tx public key: c10ad13477e9f4c0ae5d077c35b3500d263028961456417ed579eb8fb8276cc1
Timestamp: 1578687824 Timestamp [UCT]: 2020-01-10 20:23:44 Age [y:d:h:m:s]: 04:357:11:18:02
Block: 42948 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1144777 RingCT/type: yes/0
Extra: 01c10ad13477e9f4c0ae5d077c35b3500d263028961456417ed579eb8fb8276cc10211000000018a2ee0d9000000000000000000

1 output(s) for total of 442.278971258000 dcy

stealth address amount amount idx
00: 1b1ad863a3afbaeee7f025ab614951f3e4934c7ce664b9c88ac205db5d0237e6 442.278971258000 77528 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": 42958, "vin": [ { "gen": { "height": 42948 } } ], "vout": [ { "amount": 442278971258, "target": { "key": "1b1ad863a3afbaeee7f025ab614951f3e4934c7ce664b9c88ac205db5d0237e6" } } ], "extra": [ 1, 193, 10, 209, 52, 119, 233, 244, 192, 174, 93, 7, 124, 53, 179, 80, 13, 38, 48, 40, 150, 20, 86, 65, 126, 213, 121, 235, 143, 184, 39, 108, 193, 2, 17, 0, 0, 0, 1, 138, 46, 224, 217, 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