Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ae9fa06d20bca3b78f1701653269d3434d5e83a28d807f95533ef661ddc1a8a6

Tx prefix hash: cf958b42f8d4f84dc5d72f4f28632b0aba1589822b4698353c25c5cce86b40ab
Tx public key: 66880cbbccd0d2a0a459fcd75a314ccecd4e3443ffc8b8851129fc9e56493702
Timestamp: 1712260531 Timestamp [UTC]: 2024-04-04 19:55:31 Age [y:d:h:m:s]: 02:230:02:09:44
Block: 993379 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 689589 RingCT/type: yes/0
Extra: 0166880cbbccd0d2a0a459fcd75a314ccecd4e3443ffc8b8851129fc9e5649370202110000000352d47e94000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 5b4cd8bec85d5318683d3d9144f04d4b3186cf9cceec4b30c91ad93ec4fbc6a8 0.000600000000 1453765 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 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": 993389, "vin": [ { "gen": { "height": 993379 } } ], "vout": [ { "amount": 600000000, "target": { "key": "5b4cd8bec85d5318683d3d9144f04d4b3186cf9cceec4b30c91ad93ec4fbc6a8" } } ], "extra": [ 1, 102, 136, 12, 187, 204, 208, 210, 160, 164, 89, 252, 215, 90, 49, 76, 206, 205, 78, 52, 67, 255, 200, 184, 133, 17, 41, 252, 158, 86, 73, 55, 2, 2, 17, 0, 0, 0, 3, 82, 212, 126, 148, 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: