Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c2e2c32c7754ea6b2e9ddf4b08f069166bcddf516f1d37ceeb703971e7dbe0e4

Tx prefix hash: c5d267022d2d610e978ae14b58c5b8370612869134211d28c99213e0c64f6502
Tx public key: 0420aeefa37154b9b9871660602fdaf83d0c9c826872d0190a4dcbdd64a381f8
Timestamp: 1771753714 Timestamp [UTC]: 2026-02-22 09:48:34 Age [y:d:h:m:s]: 00:269:11:37:48
Block: 1483267 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 198128 RingCT/type: yes/0
Extra: 010420aeefa37154b9b9871660602fdaf83d0c9c826872d0190a4dcbdd64a381f8021100000006e4f5193f000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: c39a84ec1570a7a5ef65d30a9609eb7f17fd57d53fb23e7b129ba967759d9e75 0.000600000000 1972673 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": 1483277, "vin": [ { "gen": { "height": 1483267 } } ], "vout": [ { "amount": 600000000, "target": { "key": "c39a84ec1570a7a5ef65d30a9609eb7f17fd57d53fb23e7b129ba967759d9e75" } } ], "extra": [ 1, 4, 32, 174, 239, 163, 113, 84, 185, 185, 135, 22, 96, 96, 47, 218, 248, 61, 12, 156, 130, 104, 114, 208, 25, 10, 77, 203, 221, 100, 163, 129, 248, 2, 17, 0, 0, 0, 6, 228, 245, 25, 63, 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: