Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ed9d53b3bea5bbf8d6c55b7a9588e01663d186916d81a91b0e280a44c3e0e8df

Tx prefix hash: 87128f4d8e21015734d1cd6edac5632e948b1cfada6da7344dacbd1bc14c811a
Tx public key: f59c11f6230c86dd13dccdecf757d79566f594d4e599747c7e4aac950af82c5f
Timestamp: 1582350906 Timestamp [UCT]: 2020-02-22 05:55:06 Age [y:d:h:m:s]: 05:011:23:28:18
Block: 70118 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1161615 RingCT/type: yes/0
Extra: 01f59c11f6230c86dd13dccdecf757d79566f594d4e599747c7e4aac950af82c5f02110000000dd81c26c0000000000000000000

1 output(s) for total of 359.507773187000 dcy

stealth address amount amount idx
00: 0a2f4c364c0ac62e4e1dbf97138216a4eb9e45b144c4ddcd50ae2e6d415b2ad8 359.507773187000 129412 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": 70128, "vin": [ { "gen": { "height": 70118 } } ], "vout": [ { "amount": 359507773187, "target": { "key": "0a2f4c364c0ac62e4e1dbf97138216a4eb9e45b144c4ddcd50ae2e6d415b2ad8" } } ], "extra": [ 1, 245, 156, 17, 246, 35, 12, 134, 221, 19, 220, 205, 236, 247, 87, 215, 149, 102, 245, 148, 212, 229, 153, 116, 124, 126, 74, 172, 149, 10, 248, 44, 95, 2, 17, 0, 0, 0, 13, 216, 28, 38, 192, 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