Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 7f83d04565903a5e14c6ec25e5030b6fccf8ac1bdeb1950f331c440509bbc4bd

Tx prefix hash: 43ab9dfd96a1986f30e441b5c3dc6f339603b03a6044c5f24f956e0eca6150d3
Tx public key: f67ba6fdb48a422d99041a7fadd9daa21729f1d642a9e15cbfab00f0d306d222
Timestamp: 1729992372 Timestamp [UCT]: 2024-10-27 01:26:12 Age [y:d:h:m:s]: 00:028:06:40:38
Block: 1140368 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 20188 RingCT/type: yes/0
Extra: 01f67ba6fdb48a422d99041a7fadd9daa21729f1d642a9e15cbfab00f0d306d222021100000002007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 1d491807dd964d1dfd35e8f40fee5a76448939160f18ca9624f566cdaf44fd98 0.600000000000 1624163 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": 1140378, "vin": [ { "gen": { "height": 1140368 } } ], "vout": [ { "amount": 600000000, "target": { "key": "1d491807dd964d1dfd35e8f40fee5a76448939160f18ca9624f566cdaf44fd98" } } ], "extra": [ 1, 246, 123, 166, 253, 180, 138, 66, 45, 153, 4, 26, 127, 173, 217, 218, 162, 23, 41, 241, 214, 66, 169, 225, 92, 191, 171, 0, 240, 211, 6, 210, 34, 2, 17, 0, 0, 0, 2, 0, 127, 151, 138, 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