Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 27a33352b761d050b9d9c4df83b6962e4e2b4afc7af4a8413980604f5222906d

Tx prefix hash: 90a38a44c599388ca663b04b45f04ae00c9a0a088e7ac709d6830251b06ecfb3
Tx public key: cfa7e8f476694a0729efcb58eb865097dc6dc7d6486815f99551510a29ced35c
Timestamp: 1725911211 Timestamp [UCT]: 2024-09-09 19:46:51 Age [y:d:h:m:s]: 00:075:15:47:00
Block: 1106574 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 54080 RingCT/type: yes/0
Extra: 01cfa7e8f476694a0729efcb58eb865097dc6dc7d6486815f99551510a29ced35c021100000009e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 73c5bb982aaa09d271fd91cc43cba812cfcd056f773f956d95a33fa446e2e823 0.600000000000 1584175 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": 1106584, "vin": [ { "gen": { "height": 1106574 } } ], "vout": [ { "amount": 600000000, "target": { "key": "73c5bb982aaa09d271fd91cc43cba812cfcd056f773f956d95a33fa446e2e823" } } ], "extra": [ 1, 207, 167, 232, 244, 118, 105, 74, 7, 41, 239, 203, 88, 235, 134, 80, 151, 220, 109, 199, 214, 72, 104, 21, 249, 149, 81, 81, 10, 41, 206, 211, 92, 2, 17, 0, 0, 0, 9, 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