Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2bc4d7e3a7a0300002bba0cdb24fb4ca243b25d240b4b520f6d599a7b71067dd

Tx prefix hash: 33952d6aa12fba56aa15c9f56fd9ea742f000473a299464fd7b714cfddfddd25
Tx public key: 4864e9a52432ffa5071bfe3ec6a221568dc126de57f523f869795936fef8b4f3
Timestamp: 1742794911 Timestamp [UTC]: 2025-03-24 05:41:51 Age [y:d:h:m:s]: 01:243:05:21:45
Block: 1246048 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 437446 RingCT/type: yes/0
Extra: 014864e9a52432ffa5071bfe3ec6a221568dc126de57f523f869795936fef8b4f3021100000005c6740958000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 0fc32cfa40be468328cd7efd9ea201f5c26412e1f2cd6cb8b09cf75c83c210c2 0.000600000000 1733043 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": 1246058, "vin": [ { "gen": { "height": 1246048 } } ], "vout": [ { "amount": 600000000, "target": { "key": "0fc32cfa40be468328cd7efd9ea201f5c26412e1f2cd6cb8b09cf75c83c210c2" } } ], "extra": [ 1, 72, 100, 233, 165, 36, 50, 255, 165, 7, 27, 254, 62, 198, 162, 33, 86, 141, 193, 38, 222, 87, 245, 35, 248, 105, 121, 89, 54, 254, 248, 180, 243, 2, 17, 0, 0, 0, 5, 198, 116, 9, 88, 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: