Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 67a424a50ea4c44570ae6fb5482639d1d37f5f098682494d9b34326c921c5cfc

Tx prefix hash: ed587396c078d6d6e9d45a332de7337c6d2684225ceb43ade494162cc156764a
Tx public key: adf65772cc3c2f1e6fae8c76e926c55b6dde70667c8fdf5a24f5a288a7d8de62
Timestamp: 1713094415 Timestamp [UCT]: 2024-04-14 11:33:35 Age [y:d:h:m:s]: 00:214:15:38:52
Block: 1000283 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 153677 RingCT/type: yes/0
Extra: 01adf65772cc3c2f1e6fae8c76e926c55b6dde70667c8fdf5a24f5a288a7d8de620211000000017a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f1723d4113e045f221b9a8a4349a854c842d238628defb8f1e4bcba7d91f1ed4 0.600000000000 1460779 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": 1000293, "vin": [ { "gen": { "height": 1000283 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f1723d4113e045f221b9a8a4349a854c842d238628defb8f1e4bcba7d91f1ed4" } } ], "extra": [ 1, 173, 246, 87, 114, 204, 60, 47, 30, 111, 174, 140, 118, 233, 38, 197, 91, 109, 222, 112, 102, 124, 143, 223, 90, 36, 245, 162, 136, 167, 216, 222, 98, 2, 17, 0, 0, 0, 1, 122, 156, 244, 199, 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