Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3a20f5ab09251d0c33946196df9a86c788de29e45c261a8e1e8a2ed3b7965d36

Tx prefix hash: 3337bbdd30537f4ff8418938fdfe6e7c4ad9f8368b10f696a80a6823e5d6d59a
Tx public key: fa9543fcb24438476f75b5d3a6e5dc9f2a969c8e121bd38e92145a316917e835
Timestamp: 1772400736 Timestamp [UTC]: 2026-03-01 21:32:16 Age [y:d:h:m:s]: 00:263:23:43:55
Block: 1488614 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 194324 RingCT/type: yes/0
Extra: 01fa9543fcb24438476f75b5d3a6e5dc9f2a969c8e121bd38e92145a316917e835021100000005f188c8a8000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 08a1bdfd4cb830e40c2f5982712b72e5d7045d327841ce75f8297f023e41f798 0.000600000000 1978094 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": 1488624, "vin": [ { "gen": { "height": 1488614 } } ], "vout": [ { "amount": 600000000, "target": { "key": "08a1bdfd4cb830e40c2f5982712b72e5d7045d327841ce75f8297f023e41f798" } } ], "extra": [ 1, 250, 149, 67, 252, 178, 68, 56, 71, 111, 117, 181, 211, 166, 229, 220, 159, 42, 150, 156, 142, 18, 27, 211, 142, 146, 20, 90, 49, 105, 23, 232, 53, 2, 17, 0, 0, 0, 5, 241, 136, 200, 168, 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: