Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1fa9f84b288e773d76445831eb5fb1cf7f7921bd58b488b9e9143e52fedbc42c

Tx prefix hash: d73a51ab59ab4ab0aa292047381b4ba77087e993739a689081907d643988ada0
Tx public key: 5f59bfc532d959a7b0e8395acab2d6e151be3419388b7b19163fc827c9f3152e
Timestamp: 1706635043 Timestamp [UTC]: 2024-01-30 17:17:23 Age [y:d:h:m:s]: 02:294:06:13:24
Block: 946734 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 735505 RingCT/type: yes/0
Extra: 015f59bfc532d959a7b0e8395acab2d6e151be3419388b7b19163fc827c9f3152e02110000000652d47e94000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 37cf1dfd767ba0f86f4eed82878f6b7a2a272431c839ae999b2c6eb30c247f23 0.000600000000 1405074 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": 946744, "vin": [ { "gen": { "height": 946734 } } ], "vout": [ { "amount": 600000000, "target": { "key": "37cf1dfd767ba0f86f4eed82878f6b7a2a272431c839ae999b2c6eb30c247f23" } } ], "extra": [ 1, 95, 89, 191, 197, 50, 217, 89, 167, 176, 232, 57, 90, 202, 178, 214, 225, 81, 190, 52, 25, 56, 139, 123, 25, 22, 63, 200, 39, 201, 243, 21, 46, 2, 17, 0, 0, 0, 6, 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: