Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1ceeb08740ed2fbe81d225ed95c37916a78e60eb4cb4568cd7d64f34cc8e135f

Tx prefix hash: 403e1313477381e62fc5f2178c9a984d200bee57134bb3b0667f20798b046b7e
Tx public key: 7e2d21fa0138f2e87db9e8ff8178818395795ab4f3abe7ece37a4a8d928dba1e
Timestamp: 1774388877 Timestamp [UTC]: 2026-03-24 21:47:57 Age [y:d:h:m:s]: 00:237:04:22:16
Block: 1505061 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 175010 RingCT/type: yes/0
Extra: 017e2d21fa0138f2e87db9e8ff8178818395795ab4f3abe7ece37a4a8d928dba1e021100000004e4f5193f000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: cdb8bf2b3617e4cc639dd01a96c9de0a8a552f1245750fbcbfb66047201a930a 0.000600000000 1994793 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": 1505071, "vin": [ { "gen": { "height": 1505061 } } ], "vout": [ { "amount": 600000000, "target": { "key": "cdb8bf2b3617e4cc639dd01a96c9de0a8a552f1245750fbcbfb66047201a930a" } } ], "extra": [ 1, 126, 45, 33, 250, 1, 56, 242, 232, 125, 185, 232, 255, 129, 120, 129, 131, 149, 121, 90, 180, 243, 171, 231, 236, 227, 122, 74, 141, 146, 141, 186, 30, 2, 17, 0, 0, 0, 4, 228, 245, 25, 63, 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: