Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: bb9595a2988da85e5b2ee1980c749af50560c0e066764471cbd7ff2b3dffc60e

Tx prefix hash: eb07fd0ed1daa8d9cd47164f29d96e98e49f77072f6e46987ded21f2a443b2c5
Tx public key: dc655bf05e2296ab20e7343f1b3bcdd163dc78a17d92a058887f53cf17999568
Timestamp: 1741693864 Timestamp [UTC]: 2025-03-11 11:51:04 Age [y:d:h:m:s]: 01:252:00:03:45
Block: 1236951 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 444161 RingCT/type: yes/0
Extra: 01dc655bf05e2296ab20e7343f1b3bcdd163dc78a17d92a058887f53cf179995680211000000091f0a53eb000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 6e2d778a4768264c817c5365b199f6a2f1471487093eb26d6a8e2eaa804f2a28 0.000600000000 1723904 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": 1236961, "vin": [ { "gen": { "height": 1236951 } } ], "vout": [ { "amount": 600000000, "target": { "key": "6e2d778a4768264c817c5365b199f6a2f1471487093eb26d6a8e2eaa804f2a28" } } ], "extra": [ 1, 220, 101, 91, 240, 94, 34, 150, 171, 32, 231, 52, 63, 27, 59, 205, 209, 99, 220, 120, 161, 125, 146, 160, 88, 136, 127, 83, 207, 23, 153, 149, 104, 2, 17, 0, 0, 0, 9, 31, 10, 83, 235, 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: