Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 22fa2e5127960f18d837f698a36e0eda5a863b7cfbb2b29dc6e21de9fbfe6376

Tx prefix hash: 26989d6510c2e5ec993cc9bf3efbccac59c9745d59412f8ba477cacbab696aff
Tx public key: a22c9c19ee75bc7f362dd2b4f5bb79a64925df3cc5958aa5b1a91fa0f748e998
Timestamp: 1742074153 Timestamp [UTC]: 2025-03-15 21:29:13 Age [y:d:h:m:s]: 01:248:05:45:20
Block: 1240105 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 441491 RingCT/type: yes/0
Extra: 01a22c9c19ee75bc7f362dd2b4f5bb79a64925df3cc5958aa5b1a91fa0f748e99802110000000e1f0a53eb000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: ce0d5d51fa7c504d8a0991e97c11fdccb3b9a81a28dbfd8e122b4b160fdc2ed1 0.000600000000 1727070 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": 1240115, "vin": [ { "gen": { "height": 1240105 } } ], "vout": [ { "amount": 600000000, "target": { "key": "ce0d5d51fa7c504d8a0991e97c11fdccb3b9a81a28dbfd8e122b4b160fdc2ed1" } } ], "extra": [ 1, 162, 44, 156, 25, 238, 117, 188, 127, 54, 45, 210, 180, 245, 187, 121, 166, 73, 37, 223, 60, 197, 149, 138, 165, 177, 169, 31, 160, 247, 72, 233, 152, 2, 17, 0, 0, 0, 14, 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: