Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2ea1bd982d6ca124b4a6ebe2c402342f65068673e6d2ed256b03f7341a608492

Tx prefix hash: e25e1df5c87788984259346ac450c995d4b32ca390d87b774e50af0a1451fcc3
Tx public key: dd3e472c45e11f2cf325e5c84d0d8f6c5a76578a8611ea6ce31d0e3466c6bb1d
Timestamp: 1584766947 Timestamp [UCT]: 2020-03-21 05:02:27 Age [y:d:h:m:s]: 05:228:20:43:52
Block: 86316 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1318146 RingCT/type: yes/0
Extra: 01dd3e472c45e11f2cf325e5c84d0d8f6c5a76578a8611ea6ce31d0e3466c6bb1d02110000000569b04ac4000000000000000000

1 output(s) for total of 317.687437215000 dcy

stealth address amount amount idx
00: 145947aedb70db1d48bc059df3a4243c5146a6953774ba8c73b28f43215e92ee 317.687437215000 155692 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": 86326, "vin": [ { "gen": { "height": 86316 } } ], "vout": [ { "amount": 317687437215, "target": { "key": "145947aedb70db1d48bc059df3a4243c5146a6953774ba8c73b28f43215e92ee" } } ], "extra": [ 1, 221, 62, 71, 44, 69, 225, 31, 44, 243, 37, 229, 200, 77, 13, 143, 108, 90, 118, 87, 138, 134, 17, 234, 108, 227, 29, 14, 52, 102, 198, 187, 29, 2, 17, 0, 0, 0, 5, 105, 176, 74, 196, 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