Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 90ad829f09061a0bc437d9be5edc8ae2cd4865121312714910fc8877b2fc3356

Tx prefix hash: 248546f8f28c27f1f1787326bbd291093ee7ea06c6a03decc7697ac3a947a688
Tx public key: 4331fcb6aa3db66fead771eed358041cbc7d6a4e5e68fa1f428f89db6479ecee
Timestamp: 1774614919 Timestamp [UTC]: 2026-03-27 12:35:19 Age [y:d:h:m:s]: 00:235:12:03:04
Block: 1506931 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 173828 RingCT/type: yes/0
Extra: 014331fcb6aa3db66fead771eed358041cbc7d6a4e5e68fa1f428f89db6479ecee021100000004e4f5193f000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 758a7d26480212a6c6eddae3d653ad3eda17aa91c158e4cfe1c72e4ede0faced 0.000600000000 1996681 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": 1506941, "vin": [ { "gen": { "height": 1506931 } } ], "vout": [ { "amount": 600000000, "target": { "key": "758a7d26480212a6c6eddae3d653ad3eda17aa91c158e4cfe1c72e4ede0faced" } } ], "extra": [ 1, 67, 49, 252, 182, 170, 61, 182, 111, 234, 215, 113, 238, 211, 88, 4, 28, 188, 125, 106, 78, 94, 104, 250, 31, 66, 143, 137, 219, 100, 121, 236, 238, 2, 17, 0, 0, 0, 4, 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: