Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e2d0b99d26718bae28b8273804cd7246f767051626bad420bcccdbdc15f69ee3

Tx prefix hash: 666f0cfa930a69b504ccf59f4a85ffc7b9c09fb39d1e781d501898796b16ad2b
Tx public key: 5f079012dd834a6c3804ecb60a28b001d05d6ec1f00095678c93b69a00b6d3f8
Timestamp: 1730816907 Timestamp [UCT]: 2024-11-05 14:28:27 Age [y:d:h:m:s]: 00:018:17:09:07
Block: 1147143 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 13403 RingCT/type: yes/0
Extra: 015f079012dd834a6c3804ecb60a28b001d05d6ec1f00095678c93b69a00b6d3f80211000000011f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b3a9ff1cb718ab806fae988f37afaedd39ab01b9e3485c8321b10db508142f01 0.600000000000 1631836 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": 1147153, "vin": [ { "gen": { "height": 1147143 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b3a9ff1cb718ab806fae988f37afaedd39ab01b9e3485c8321b10db508142f01" } } ], "extra": [ 1, 95, 7, 144, 18, 221, 131, 74, 108, 56, 4, 236, 182, 10, 40, 176, 1, 208, 93, 110, 193, 240, 0, 149, 103, 140, 147, 182, 154, 0, 182, 211, 248, 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