Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a7b8d477249082fe1de1d39b5b390f6a8df5e2b91271d4e901d8aa2ccfa62a5d

Tx prefix hash: a3bd191e83fa65123f23b92dc9ecd726017048ee8694d1671a49ed5b5c2bd258
Tx public key: a6d6d2488f36e5021fa13e2391080ed7c27c44eb20bfbe64d28c4ee753d710ec
Timestamp: 1790934290 Timestamp [UTC]: 2026-10-02 09:44:50 Age [y:d:h:m:s]: 00:042:11:26:33
Block: 1646823 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0820 kB
Tx version: 2 No of confirmations: 30840 RingCT/type: yes/0
Extra: 01a6d6d2488f36e5021fa13e2391080ed7c27c44eb20bfbe64d28c4ee753d710ec

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: a8574c671feb422239409f440ca573a84619fe09e25810f0f771d33b35f64a6a 0.000600000000 2136979 of 15 <95>

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": 1646833, "vin": [ { "gen": { "height": 1646823 } } ], "vout": [ { "amount": 600000000, "target": { "tagged_key": { "key": "a8574c671feb422239409f440ca573a84619fe09e25810f0f771d33b35f64a6a", "view_tag": "95" } } } ], "extra": [ 1, 166, 214, 210, 72, 143, 54, 229, 2, 31, 161, 62, 35, 145, 8, 14, 215, 194, 124, 68, 235, 32, 191, 190, 100, 210, 140, 78, 231, 83, 215, 16, 236 ], "rct_signatures": { "type": 0 } }


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