Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: cb65a7d4158d720a85e4e755a684b6544ee091e334a38437d73e3b0d0064ffa6

Tx prefix hash: 30c83d19b5596a686df0501762a33bf6ce1fbf6999b4569e6ed7aff2a4ef4ab4
Tx public key: b74fd27a0d7b12ea929fa0e40d1a22d9032bede9626d39e82dc19e6812fa2c2c
Timestamp: 1773791054 Timestamp [UTC]: 2026-03-17 23:44:14 Age [y:d:h:m:s]: 00:241:13:38:19
Block: 1500107 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 178062 RingCT/type: yes/0
Extra: 01b74fd27a0d7b12ea929fa0e40d1a22d9032bede9626d39e82dc19e6812fa2c2c021100000007f188c8a8000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: cd91a42475a8c58f8d8be6927009c006e5f827a0612f5f91b9ec5e8fa9562fda 0.000600000000 1989777 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": 1500117, "vin": [ { "gen": { "height": 1500107 } } ], "vout": [ { "amount": 600000000, "target": { "key": "cd91a42475a8c58f8d8be6927009c006e5f827a0612f5f91b9ec5e8fa9562fda" } } ], "extra": [ 1, 183, 79, 210, 122, 13, 123, 18, 234, 146, 159, 160, 228, 13, 26, 34, 217, 3, 43, 237, 233, 98, 109, 57, 232, 45, 193, 158, 104, 18, 250, 44, 44, 2, 17, 0, 0, 0, 7, 241, 136, 200, 168, 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: