Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: efb46f3a1c38283d91780cd5b7e1bf412df89bd57c4746202adde1695d494518

Tx prefix hash: 8d9e4c50ab856d183e33a38807c7d583e88cba503021541aa9f5b53970c3e055
Tx public key: f85d2e06a1f950129595bf06302938c2f3db00dd2c5d649c391339a4180342a2
Timestamp: 1737192739 Timestamp [UCT]: 2025-01-18 09:32:19 Age [y:d:h:m:s]: 00:153:06:29:19
Block: 1199943 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 109216 RingCT/type: yes/0
Extra: 01f85d2e06a1f950129595bf06302938c2f3db00dd2c5d649c391339a4180342a20211000000031f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: cac665f9e6dd0fc23c735e92351ec2a881c5daa667b9f628a7368b363251f1a2 0.600000000000 1686582 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": 1199953, "vin": [ { "gen": { "height": 1199943 } } ], "vout": [ { "amount": 600000000, "target": { "key": "cac665f9e6dd0fc23c735e92351ec2a881c5daa667b9f628a7368b363251f1a2" } } ], "extra": [ 1, 248, 93, 46, 6, 161, 249, 80, 18, 149, 149, 191, 6, 48, 41, 56, 194, 243, 219, 0, 221, 44, 93, 100, 156, 57, 19, 57, 164, 24, 3, 66, 162, 2, 17, 0, 0, 0, 3, 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