Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e3ba72803314e2ed7c2d7ffd5f6dcd236c6462c164dfdbb75ff40eb3776a3a9a

Tx prefix hash: da5121e1aced389e9e5d7a95fb8dfd79ab42756d34948888c54a52555584a700
Tx public key: 1dd19d7851240d77a69c403262c24f93f5f39e8d5acad5ac342e75e5ca167951
Timestamp: 1744702755 Timestamp [UTC]: 2025-04-15 07:39:15 Age [y:d:h:m:s]: 01:213:07:05:42
Block: 1261844 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 416356 RingCT/type: yes/0
Extra: 011dd19d7851240d77a69c403262c24f93f5f39e8d5acad5ac342e75e5ca1679510211000000066c98aa3d000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 726d82f5c41beb7b64ae2898b73899b7387363ac024bda91583eb7f1a0a6e956 0.000600000000 1749019 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": 1261854, "vin": [ { "gen": { "height": 1261844 } } ], "vout": [ { "amount": 600000000, "target": { "key": "726d82f5c41beb7b64ae2898b73899b7387363ac024bda91583eb7f1a0a6e956" } } ], "extra": [ 1, 29, 209, 157, 120, 81, 36, 13, 119, 166, 156, 64, 50, 98, 194, 79, 147, 245, 243, 158, 141, 90, 202, 213, 172, 52, 46, 117, 229, 202, 22, 121, 81, 2, 17, 0, 0, 0, 6, 108, 152, 170, 61, 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: