Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b01bbb516877508bc1f1ea6a1001e59ad98956462f3b54172cda5393dcf4c0bc

Tx prefix hash: eafbbfef95df7ea75cd6f80dccd1c62abdfe79bd13afb8c8ea1f511ae46b04e9
Tx public key: fd65a9ec7afc9ee88f76fb18a9ac9593e430daf1fec896ea2d6fc0f347d408aa
Timestamp: 1582967507 Timestamp [UCT]: 2020-02-29 09:11:47 Age [y:d:h:m:s]: 05:004:23:00:04
Block: 73855 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1157971 RingCT/type: yes/0
Extra: 01fd65a9ec7afc9ee88f76fb18a9ac9593e430daf1fec896ea2d6fc0f347d408aa0211000000044943cd9f000000000000000000

1 output(s) for total of 349.380155314000 dcy

stealth address amount amount idx
00: 243c27fb73a8c8917df2aa1a9d0ccf14d827a9c714d62c93a3cff47f154e23c3 349.380155314000 136468 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": 73865, "vin": [ { "gen": { "height": 73855 } } ], "vout": [ { "amount": 349380155314, "target": { "key": "243c27fb73a8c8917df2aa1a9d0ccf14d827a9c714d62c93a3cff47f154e23c3" } } ], "extra": [ 1, 253, 101, 169, 236, 122, 252, 158, 232, 143, 118, 251, 24, 169, 172, 149, 147, 228, 48, 218, 241, 254, 200, 150, 234, 45, 111, 192, 243, 71, 212, 8, 170, 2, 17, 0, 0, 0, 4, 73, 67, 205, 159, 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