Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3bc8827cda60461d181bb85cc87d492bbd4e32b2ea53b27de6681c957aa12d48

Tx prefix hash: fd1400efbc7fa8aeace9e972ef77b02fb4f7aa43a7b94a46dfa3b32e15c86199
Tx public key: a4564cfe6dbf15064e3920df4e9767ecaedbefd685f0df57cd28229454456eeb
Timestamp: 1708279287 Timestamp [UCT]: 2024-02-18 18:01:27 Age [y:d:h:m:s]: 01:259:16:44:33
Block: 960384 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 444353 RingCT/type: yes/0
Extra: 01a4564cfe6dbf15064e3920df4e9767ecaedbefd685f0df57cd28229454456eeb0211000000010011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 2e2c3a0cb0b5fc9e4b631559333c0da4b1d0db1ea6e41b31c4f97cd701e21835 0.600000000000 1419947 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": 960394, "vin": [ { "gen": { "height": 960384 } } ], "vout": [ { "amount": 600000000, "target": { "key": "2e2c3a0cb0b5fc9e4b631559333c0da4b1d0db1ea6e41b31c4f97cd701e21835" } } ], "extra": [ 1, 164, 86, 76, 254, 109, 191, 21, 6, 78, 57, 32, 223, 78, 151, 103, 236, 174, 219, 239, 214, 133, 240, 223, 87, 205, 40, 34, 148, 84, 69, 110, 235, 2, 17, 0, 0, 0, 1, 0, 17, 5, 91, 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