Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3e77c58276a9b3119404601273d04e8c4249abea40ecac9add76cb64c6a3765f

Tx prefix hash: 71e317fddf82ea7f001ad71c1cba1d8debe053d03d5cbd9010738104881ea8b1
Tx public key: 2a8ed515e8d3db565bbd610b96dd9ac6c3ff89b3a408923f91269282951b057e
Timestamp: 1580977438 Timestamp [UCT]: 2020-02-06 08:23:58 Age [y:d:h:m:s]: 04:293:20:51:45
Block: 59722 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1101457 RingCT/type: yes/0
Extra: 012a8ed515e8d3db565bbd610b96dd9ac6c3ff89b3a408923f91269282951b057e02110000000403d36d11000000000000000000

1 output(s) for total of 389.150005530000 dcy

stealth address amount amount idx
00: 2432fa030741745de50aaeb60ac7974ed969aafdc356754635494329f9912a22 389.150005530000 110208 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": 59732, "vin": [ { "gen": { "height": 59722 } } ], "vout": [ { "amount": 389150005530, "target": { "key": "2432fa030741745de50aaeb60ac7974ed969aafdc356754635494329f9912a22" } } ], "extra": [ 1, 42, 142, 213, 21, 232, 211, 219, 86, 91, 189, 97, 11, 150, 221, 154, 198, 195, 255, 137, 179, 164, 8, 146, 63, 145, 38, 146, 130, 149, 27, 5, 126, 2, 17, 0, 0, 0, 4, 3, 211, 109, 17, 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