Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b85a1077f885547943390b9aa4d4e68ff4975d0ae362ecdf3c7cdcba29b05439

Tx prefix hash: 801b60e4b0b1f46b88564149109293366ca1323c1197550f40d2bfa76a141130
Tx public key: cce75facd0227972f9a2f055039f62a3dd6aafde61946343e5e1d724a9df412a
Timestamp: 1717076103 Timestamp [UCT]: 2024-05-30 13:35:03 Age [y:d:h:m:s]: 00:332:10:37:20
Block: 1033316 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 237616 RingCT/type: yes/0
Extra: 01cce75facd0227972f9a2f055039f62a3dd6aafde61946343e5e1d724a9df412a0211000000067a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 81845bf3f3d2c4dd62b761e2c185bb10393aff152a31764d9cfc43c1244b4262 0.600000000000 1501781 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": 1033326, "vin": [ { "gen": { "height": 1033316 } } ], "vout": [ { "amount": 600000000, "target": { "key": "81845bf3f3d2c4dd62b761e2c185bb10393aff152a31764d9cfc43c1244b4262" } } ], "extra": [ 1, 204, 231, 95, 172, 208, 34, 121, 114, 249, 162, 240, 85, 3, 159, 98, 163, 221, 106, 175, 222, 97, 148, 99, 67, 229, 225, 215, 36, 169, 223, 65, 42, 2, 17, 0, 0, 0, 6, 122, 156, 244, 199, 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