Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 43c717248e47c59502a8dd8ac000a5fbf1f1db3873febc2d63f7cf765022c930

Tx prefix hash: d04fa41889823e92af938b898cea4475fc59a16266c3650e5699b97394b3ba26
Tx public key: 85f91e58dfaf63d9a7598a24e632a9af3b7c39a92d330610a28e5b3cec8eccfa
Timestamp: 1733303241 Timestamp [UCT]: 2024-12-04 09:07:21 Age [y:d:h:m:s]: 00:110:05:36:11
Block: 1167742 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 78581 RingCT/type: yes/0
Extra: 0185f91e58dfaf63d9a7598a24e632a9af3b7c39a92d330610a28e5b3cec8eccfa0211000000021f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b600dc10e2340acffc5cd2df5cad31e8a7234f496d313769ba5c5cc1880a2976 0.600000000000 1653443 of 15

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": 1167752, "vin": [ { "gen": { "height": 1167742 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b600dc10e2340acffc5cd2df5cad31e8a7234f496d313769ba5c5cc1880a2976" } } ], "extra": [ 1, 133, 249, 30, 88, 223, 175, 99, 217, 167, 89, 138, 36, 230, 50, 169, 175, 59, 124, 57, 169, 45, 51, 6, 16, 162, 142, 91, 60, 236, 142, 204, 250, 2, 17, 0, 0, 0, 2, 31, 10, 83, 235, 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