Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 935359f3fa4ff0e4c7654f61c8bd71a2e703841c3687a0ed1c8894a7e417b4db

Tx prefix hash: 04f6c21b702796cb3ecd3019c61d3cb618f253a1b4117d0aeb58b3faceadb62f
Tx public key: dc98d6089fed952068c28ec2e76894c4ba5579cfef575c392f54c9864a1412e5
Timestamp: 1696032585 Timestamp [UTC]: 2023-09-30 00:09:45 Age [y:d:h:m:s]: 03:054:05:04:26
Block: 859060 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 824434 RingCT/type: yes/0
Extra: 01dc98d6089fed952068c28ec2e76894c4ba5579cfef575c392f54c9864a1412e50211000000104b8f5122000000000000000000

1 output(s) for total of 0.000874133271 xmr

stealth address amount amount idx tag
00: 64d66e614774a7beebcd073b5af90af9893a8f7bf20aea9f0e0248f858e0b80b 0.000874133271 1313268 of 0 -

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 dinastycoin-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": 859070, "vin": [ { "gen": { "height": 859060 } } ], "vout": [ { "amount": 874133271, "target": { "key": "64d66e614774a7beebcd073b5af90af9893a8f7bf20aea9f0e0248f858e0b80b" } } ], "extra": [ 1, 220, 152, 214, 8, 159, 237, 149, 32, 104, 194, 142, 194, 231, 104, 148, 196, 186, 85, 121, 207, 239, 87, 92, 57, 47, 84, 201, 134, 74, 20, 18, 229, 2, 17, 0, 0, 0, 16, 75, 143, 81, 34, 0, 0, 0, 0, 0, 0, 0, 0, 0 ], "rct_signatures": { "type": 0 } }


Less details
source code | explorer version (api): devel-2026-02-02-6303d2a (1.2) | monero version: