Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b2cfbb24cfbe63b8f8749fe275d7936f3bb83e9ce72a636b103f0c6b4571df1b

Tx prefix hash: ca7ba636f690db4ffa12c1f1182396f6c062d8e8d08515602044979d4af6dc71
Tx public key: d35dde3b3f749379b7dd0889f70db6bda36bac58d7c71a1d8eef65c0c926e548
Timestamp: 1748907204 Timestamp [UTC]: 2025-06-02 23:33:24 Age [y:d:h:m:s]: 01:165:13:10:16
Block: 1296669 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 382229 RingCT/type: yes/0
Extra: 01d35dde3b3f749379b7dd0889f70db6bda36bac58d7c71a1d8eef65c0c926e548021100000002bf51b2a2000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: b894e570b7079654ccdbb2c3749b835c8f41917baab6df7150e843d4e07cb183 0.000600000000 1784182 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": 1296679, "vin": [ { "gen": { "height": 1296669 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b894e570b7079654ccdbb2c3749b835c8f41917baab6df7150e843d4e07cb183" } } ], "extra": [ 1, 211, 93, 222, 59, 63, 116, 147, 121, 183, 221, 8, 137, 247, 13, 182, 189, 163, 107, 172, 88, 215, 199, 26, 29, 142, 239, 101, 192, 201, 38, 229, 72, 2, 17, 0, 0, 0, 2, 191, 81, 178, 162, 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: