Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 22bca4ed224dfe10e101581005832b57bb1cc06e4dc221a75a9bb61a970f33d1

Tx prefix hash: cfccc655f14a35245c0c024d6e92f72d8f603278e1c3fdba9dffea73416803e6
Tx public key: f91ffdc50bc40147a3585afdf22ac881194e12c692beda4d0fbf50311cf28445
Timestamp: 1748843754 Timestamp [UTC]: 2025-06-02 05:55:54 Age [y:d:h:m:s]: 01:173:03:46:02
Block: 1296149 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 387345 RingCT/type: yes/0
Extra: 01f91ffdc50bc40147a3585afdf22ac881194e12c692beda4d0fbf50311cf28445021100000004bf51b2a2000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 682e03cdfdd5d0324ac3585cd5692b6e0e45e47ed27c1b0012e7291f5b2f36e6 0.000600000000 1783656 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": 1296159, "vin": [ { "gen": { "height": 1296149 } } ], "vout": [ { "amount": 600000000, "target": { "key": "682e03cdfdd5d0324ac3585cd5692b6e0e45e47ed27c1b0012e7291f5b2f36e6" } } ], "extra": [ 1, 249, 31, 253, 197, 11, 196, 1, 71, 163, 88, 90, 253, 242, 42, 200, 129, 25, 78, 18, 198, 146, 190, 218, 77, 15, 191, 80, 49, 28, 242, 132, 69, 2, 17, 0, 0, 0, 4, 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: