Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 9a38826acdf982fcec9b8e940a25dd8236410db7a76e114f7e4b28079357783d

Tx prefix hash: 3fc164a9c72740ccb43e49acb31184278379a503b4e6d65eabbac101da1c1487
Tx public key: e9201cf4b0b1640253d27d978c3defe926a0b0f7361c7dd8452f771aad43ea60
Timestamp: 1733353212 Timestamp [UCT]: 2024-12-04 23:00:12 Age [y:d:h:m:s]: 00:114:21:48:34
Block: 1168159 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 81928 RingCT/type: yes/0
Extra: 01e9201cf4b0b1640253d27d978c3defe926a0b0f7361c7dd8452f771aad43ea600211000000011f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: c5498cd8b52c125af0d74c78d29d7cd9d248d8321a6e2b1f4512ba812c2e8a89 0.600000000000 1653866 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": 1168169, "vin": [ { "gen": { "height": 1168159 } } ], "vout": [ { "amount": 600000000, "target": { "key": "c5498cd8b52c125af0d74c78d29d7cd9d248d8321a6e2b1f4512ba812c2e8a89" } } ], "extra": [ 1, 233, 32, 28, 244, 176, 177, 100, 2, 83, 210, 125, 151, 140, 61, 239, 233, 38, 160, 176, 247, 54, 28, 125, 216, 69, 47, 119, 26, 173, 67, 234, 96, 2, 17, 0, 0, 0, 1, 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