Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: affa2bfc887848fc6124bbcc6767c62e354815fa9c2f2c851528af1276aa3dd3

Tx prefix hash: b991f4505c30129d48344389032846b9d98abdf1da2e0ac1133cd4c07adca671
Tx public key: cc54b6e8e5fc282e590a7ac8932efe39d631e201084590c639d375333937e25d
Timestamp: 1760934307 Timestamp [UTC]: 2025-10-20 04:25:07 Age [y:d:h:m:s]: 01:028:17:24:31
Block: 1393816 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 286853 RingCT/type: yes/0
Extra: 01cc54b6e8e5fc282e590a7ac8932efe39d631e201084590c639d375333937e25d02110000000825a35a0f000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 9dc45b997747576a246a63e115c7fb170921aa8b40b338744c4a3f580d2f5577 0.000600000000 1882083 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": 1393826, "vin": [ { "gen": { "height": 1393816 } } ], "vout": [ { "amount": 600000000, "target": { "key": "9dc45b997747576a246a63e115c7fb170921aa8b40b338744c4a3f580d2f5577" } } ], "extra": [ 1, 204, 84, 182, 232, 229, 252, 40, 46, 89, 10, 122, 200, 147, 46, 254, 57, 214, 49, 226, 1, 8, 69, 144, 198, 57, 211, 117, 51, 57, 55, 226, 93, 2, 17, 0, 0, 0, 8, 37, 163, 90, 15, 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: