Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b2c32401961809cbcf38e58beae7093c033c8ae5f2d32d3f0d667a315432212a

Tx prefix hash: eb27086264e35daff04c9da56725e32a4edead307e062dec3e17a86ebdaf6334
Tx public key: b950f664890be7875df4f620c2ac162b8d97118c1f41728cbe11d27dfb4ef7dc
Timestamp: 1735544623 Timestamp [UCT]: 2024-12-30 07:43:43 Age [y:d:h:m:s]: 00:170:06:27:17
Block: 1186288 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 121408 RingCT/type: yes/0
Extra: 01b950f664890be7875df4f620c2ac162b8d97118c1f41728cbe11d27dfb4ef7dc021100000002007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a9989afe499c2fb57ed5d0d190f5bd83057ddf3b46573534e5353e33b5228fde 0.600000000000 1672767 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": 1186298, "vin": [ { "gen": { "height": 1186288 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a9989afe499c2fb57ed5d0d190f5bd83057ddf3b46573534e5353e33b5228fde" } } ], "extra": [ 1, 185, 80, 246, 100, 137, 11, 231, 135, 93, 244, 246, 32, 194, 172, 22, 43, 141, 151, 17, 140, 31, 65, 114, 140, 190, 17, 210, 125, 251, 78, 247, 220, 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