Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 22bb5a18ebfe982675dfcbcaa2642ccd03e2b8f604c8e0340c0f9c69f95d38b7

Tx prefix hash: 855e3445e8a206d3281630e69a2a78ee9a454181b6df190dd0107aa528ba6933
Tx public key: f3807cbce98fc0d41b90fdbba943839ba039c45da0d8ce98a76411be5c425007
Timestamp: 1775265988 Timestamp [UTC]: 2026-04-04 01:26:28 Age [y:d:h:m:s]: 00:224:04:52:22
Block: 1512327 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 165623 RingCT/type: yes/0
Extra: 01f3807cbce98fc0d41b90fdbba943839ba039c45da0d8ce98a76411be5c425007021100000007ee4b7181000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 464db991fb1a61a4fd7ee86115bcce9979b4e001da22dae68c78806886d1359b 0.000600000000 2002127 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": 1512337, "vin": [ { "gen": { "height": 1512327 } } ], "vout": [ { "amount": 600000000, "target": { "key": "464db991fb1a61a4fd7ee86115bcce9979b4e001da22dae68c78806886d1359b" } } ], "extra": [ 1, 243, 128, 124, 188, 233, 143, 192, 212, 27, 144, 253, 187, 169, 67, 131, 155, 160, 57, 196, 93, 160, 216, 206, 152, 167, 100, 17, 190, 92, 66, 80, 7, 2, 17, 0, 0, 0, 7, 238, 75, 113, 129, 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: