Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 28c558a347b536f45a65e8bdbb4bdf76f751bc8caa5c7e9854e3f15d33ce7209

Tx prefix hash: 8e72b55a4dcf2676f6d1763c249e3df6bae91e3ee2b8d8af2bf5b5d9c021a191
Tx public key: 74c915b6a63e55efa7da5f5bf75809f867fbb18d92c978f809406bc9b4b0dfcd
Timestamp: 1747897000 Timestamp [UTC]: 2025-05-22 06:56:40 Age [y:d:h:m:s]: 01:005:23:54:16
Block: 1288303 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 256837 RingCT/type: yes/0
Extra: 0174c915b6a63e55efa7da5f5bf75809f867fbb18d92c978f809406bc9b4b0dfcd02110000000101491f88000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 857f39330f5410d41beadcc334dc0a2e6caccc450f33fe3de0b02bd754ee2ec7 0.000600000000 1775770 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": 1288313, "vin": [ { "gen": { "height": 1288303 } } ], "vout": [ { "amount": 600000000, "target": { "key": "857f39330f5410d41beadcc334dc0a2e6caccc450f33fe3de0b02bd754ee2ec7" } } ], "extra": [ 1, 116, 201, 21, 182, 166, 62, 85, 239, 167, 218, 95, 91, 247, 88, 9, 248, 103, 251, 177, 141, 146, 201, 120, 248, 9, 64, 107, 201, 180, 176, 223, 205, 2, 17, 0, 0, 0, 1, 1, 73, 31, 136, 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: