Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 8d269edd341ae4ceee75b145581fbc85cf7901ea34d4e478c51d241daa937909

Tx prefix hash: 47f82a3ff79432840f17ee614fd45d45d640f06b73f2f786cc1fbf8bdf808f93
Tx public key: b4afb93339ca460eaccb590aa2d71ba82bc2ec7a04df6f3cd5ac21d7158ff999
Timestamp: 1576643709 Timestamp [UCT]: 2019-12-18 04:35:09 Age [y:d:h:m:s]: 05:319:07:32:20
Block: 28361 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1373555 RingCT/type: yes/0
Extra: 01b4afb93339ca460eaccb590aa2d71ba82bc2ec7a04df6f3cd5ac21d7158ff9990211000000479159db1e000000000000000000

1 output(s) for total of 494.343807760000 dcy

stealth address amount amount idx
00: 12bb18c942e9abe611d68178fec54083c3eae938186aa6b82622499a710a7e41 494.343807760000 46905 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": 28371, "vin": [ { "gen": { "height": 28361 } } ], "vout": [ { "amount": 494343807760, "target": { "key": "12bb18c942e9abe611d68178fec54083c3eae938186aa6b82622499a710a7e41" } } ], "extra": [ 1, 180, 175, 185, 51, 57, 202, 70, 14, 172, 203, 89, 10, 162, 215, 27, 168, 43, 194, 236, 122, 4, 223, 111, 60, 213, 172, 33, 215, 21, 143, 249, 153, 2, 17, 0, 0, 0, 71, 145, 89, 219, 30, 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