Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 401d91bc084e50998e6a06043af4eabd80f7965e0773242524a83864facce3f1

Tx prefix hash: 89dae356932fcf186fe43741e10c97022ae76844f8edd3910dfbc32dc2fe2653
Tx public key: 70d351aba7a7d40f15a90a087cc25cbafe4aaf3560d00b2faf6be4a073ae2c33
Timestamp: 1779926992 Timestamp [UTC]: 2026-05-28 00:09:52 Age [y:d:h:m:s]: 00:170:12:33:12
Block: 1544921 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0820 kB
Tx version: 2 No of confirmations: 133221 RingCT/type: yes/0
Extra: 0170d351aba7a7d40f15a90a087cc25cbafe4aaf3560d00b2faf6be4a073ae2c33

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: a4a1bab5c75571a496e4ea908900b09d2e03f62c7b43c508b9dec46c8950e40d 0.000600000000 2034877 of 15 <28>

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": 1544931, "vin": [ { "gen": { "height": 1544921 } } ], "vout": [ { "amount": 600000000, "target": { "tagged_key": { "key": "a4a1bab5c75571a496e4ea908900b09d2e03f62c7b43c508b9dec46c8950e40d", "view_tag": "28" } } } ], "extra": [ 1, 112, 211, 81, 171, 167, 167, 212, 15, 21, 169, 10, 8, 124, 194, 92, 186, 254, 74, 175, 53, 96, 208, 11, 47, 175, 107, 228, 160, 115, 174, 44, 51 ], "rct_signatures": { "type": 0 } }


Less details
source code | explorer version (api): devel-2026-02-02-6303d2a (1.2) | monero version: