Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 95cb4ac0bec929445c32bfc5c5c25b7cda74d9dba50bfc888fff6de7567d677e

Tx prefix hash: 0a84561bbc87d83fb6699851486a5e226750c62ba03cbb5671ae22902e53d732
Tx public key: 42915f584efbf265476ed1674433cc5fdf8eb67946fa5117f43bfc4e54c44890
Timestamp: 1767903964 Timestamp [UTC]: 2026-01-08 20:26:04 Age [y:d:h:m:s]: 00:315:20:53:47
Block: 1451574 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 231278 RingCT/type: yes/0
Extra: 0142915f584efbf265476ed1674433cc5fdf8eb67946fa5117f43bfc4e54c4489002110000000c215bbf89000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: edb5536694fc5eae0f9251c8cb490e9b9a9a58c465929e66d4c1c6a0b8d6c0b0 0.000600000000 1940586 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": 1451584, "vin": [ { "gen": { "height": 1451574 } } ], "vout": [ { "amount": 600000000, "target": { "key": "edb5536694fc5eae0f9251c8cb490e9b9a9a58c465929e66d4c1c6a0b8d6c0b0" } } ], "extra": [ 1, 66, 145, 95, 88, 78, 251, 242, 101, 71, 110, 209, 103, 68, 51, 204, 95, 223, 142, 182, 121, 70, 250, 81, 23, 244, 59, 252, 78, 84, 196, 72, 144, 2, 17, 0, 0, 0, 12, 33, 91, 191, 137, 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: