Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a730516bfcb478f833691de94faaf38cf161862d7d8afc7eee7f0c591a87f692

Tx prefix hash: b859ee887ec31f9ded5d71b7d4305d696f41f378d2a33747aa5ba846157af695
Tx public key: 85537f3146a5bae90ebe078f34b07c604587711f7b5f244020e2f5ef394484f0
Timestamp: 1741375740 Timestamp [UTC]: 2025-03-07 19:29:00 Age [y:d:h:m:s]: 01:065:14:28:30
Block: 1234319 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 297709 RingCT/type: yes/0
Extra: 0185537f3146a5bae90ebe078f34b07c604587711f7b5f244020e2f5ef394484f002110000000e1f0a53eb000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 3afa9162a3eee6b183a6c3b2f0316cc7f557fdd3aace810581c48b5878daa058 0.000600000000 1721246 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": 1234329, "vin": [ { "gen": { "height": 1234319 } } ], "vout": [ { "amount": 600000000, "target": { "key": "3afa9162a3eee6b183a6c3b2f0316cc7f557fdd3aace810581c48b5878daa058" } } ], "extra": [ 1, 133, 83, 127, 49, 70, 165, 186, 233, 14, 190, 7, 143, 52, 176, 124, 96, 69, 135, 113, 31, 123, 95, 36, 64, 32, 226, 245, 239, 57, 68, 132, 240, 2, 17, 0, 0, 0, 14, 31, 10, 83, 235, 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: