Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f32022077f970d963eecd27a57c63195eb13fb4ad7d3aa117a15e4f52ed3629c

Tx prefix hash: c6b98ce2dd181c4b4cac12987a0aff340cfeddd1826857dbbd6eabb65c3942aa
Tx public key: d0d0cfb24bb21e944d93ef98bd9427124a1f560d55f7d2d49183eb5c943f0f8c
Timestamp: 1723332597 Timestamp [UCT]: 2024-08-10 23:29:57 Age [y:d:h:m:s]: 00:238:18:09:42
Block: 1085183 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 170515 RingCT/type: yes/0
Extra: 01d0d0cfb24bb21e944d93ef98bd9427124a1f560d55f7d2d49183eb5c943f0f8c021100000004e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 2c766f9122b3d833969b4a71f99fc21fdde76f13393db519e0a92047a655cfd6 0.600000000000 1559712 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": 1085193, "vin": [ { "gen": { "height": 1085183 } } ], "vout": [ { "amount": 600000000, "target": { "key": "2c766f9122b3d833969b4a71f99fc21fdde76f13393db519e0a92047a655cfd6" } } ], "extra": [ 1, 208, 208, 207, 178, 75, 178, 30, 148, 77, 147, 239, 152, 189, 148, 39, 18, 74, 31, 86, 13, 85, 247, 210, 212, 145, 131, 235, 92, 148, 63, 15, 140, 2, 17, 0, 0, 0, 4, 233, 20, 221, 21, 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