Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d752c3f3adef450915caa5ebc2fced1ad608163d5cb1d1efa2d92967884492ec

Tx prefix hash: 295a7cfd499cfde243411780f84c876226d9ce4469a478061151121f10d0c4ba
Tx public key: fefaf1795790944904d181815e80684384216cdadc4c6dcbd4e4d51cf74773ce
Timestamp: 1580873032 Timestamp [UCT]: 2020-02-05 03:23:52 Age [y:d:h:m:s]: 04:338:12:41:30
Block: 58692 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1133580 RingCT/type: yes/0
Extra: 01fefaf1795790944904d181815e80684384216cdadc4c6dcbd4e4d51cf74773ce02110000000149b77a3d000000000000000000

1 output(s) for total of 392.226892610000 dcy

stealth address amount amount idx
00: 9c5d2dbf90e8619d277fca5f5d0e6a7845579477a5c5dc6c72602593a6cad4b2 392.226892610000 108502 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": 58702, "vin": [ { "gen": { "height": 58692 } } ], "vout": [ { "amount": 392226892610, "target": { "key": "9c5d2dbf90e8619d277fca5f5d0e6a7845579477a5c5dc6c72602593a6cad4b2" } } ], "extra": [ 1, 254, 250, 241, 121, 87, 144, 148, 73, 4, 209, 129, 129, 94, 128, 104, 67, 132, 33, 108, 218, 220, 76, 109, 203, 212, 228, 213, 28, 247, 71, 115, 206, 2, 17, 0, 0, 0, 1, 73, 183, 122, 61, 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