Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f3c03e450c8ed1365ed3ddf707ba5053562ffc8e7a25a0377575375a69cddeb5

Tx prefix hash: cb2de2e4c18dc3d6176833d8b0c7f2e362abe1e918efa09203c5dc8f75c42fdf
Tx public key: f16062436c7d6b4d5b54da867511f528dc2f3d461a6402f92c84e0590e146168
Timestamp: 1574554807 Timestamp [UCT]: 2019-11-24 00:20:07 Age [y:d:h:m:s]: 05:102:09:41:47
Block: 16030 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0986 kB
Tx version: 2 No of confirmations: 1215845 RingCT/type: yes/0
Extra: 01f16062436c7d6b4d5b54da867511f528dc2f3d461a6402f92c84e0590e14616802110000001ef95225a5000000000000000000

1 output(s) for total of 543.120828183000 dcy

stealth address amount amount idx
00: a968423556f1d7eccfdb8b9688e2df1c31f1044c2dd518ded6b9a9efb0a6a88f 543.120828183000 22087 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": 16040, "vin": [ { "gen": { "height": 16030 } } ], "vout": [ { "amount": 543120828183, "target": { "key": "a968423556f1d7eccfdb8b9688e2df1c31f1044c2dd518ded6b9a9efb0a6a88f" } } ], "extra": [ 1, 241, 96, 98, 67, 108, 125, 107, 77, 91, 84, 218, 134, 117, 17, 245, 40, 220, 47, 61, 70, 26, 100, 2, 249, 44, 132, 224, 89, 14, 20, 97, 104, 2, 17, 0, 0, 0, 30, 249, 82, 37, 165, 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