Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e82d50d106e1d17f1b0445be21c2714cbd30cd8fa010b8937d633a2f4ff1550e

Tx prefix hash: 3d997587ff2f0191e38e6ae25cf8ce9de76fc58318bbb0293c669d1bae9de034
Tx public key: 4121c09b0aa8e89c712b63a25a37c72b04836bf8f016470e0f30638185546d76
Timestamp: 1743722670 Timestamp [UTC]: 2025-04-03 23:24:30 Age [y:d:h:m:s]: 01:108:05:08:16
Block: 1253731 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 329383 RingCT/type: yes/0
Extra: 014121c09b0aa8e89c712b63a25a37c72b04836bf8f016470e0f30638185546d760211000000054060f6d2000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: dd033cd8a9c2a2c99ec646163a6202b9fd2026fb1c26647997ce5963632b008e 0.000600000000 1740812 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": 1253741, "vin": [ { "gen": { "height": 1253731 } } ], "vout": [ { "amount": 600000000, "target": { "key": "dd033cd8a9c2a2c99ec646163a6202b9fd2026fb1c26647997ce5963632b008e" } } ], "extra": [ 1, 65, 33, 192, 155, 10, 168, 232, 156, 113, 43, 99, 162, 90, 55, 199, 43, 4, 131, 107, 248, 240, 22, 71, 14, 15, 48, 99, 129, 133, 84, 109, 118, 2, 17, 0, 0, 0, 5, 64, 96, 246, 210, 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: