Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a946c1f26ae2bc4f4fb94fed2dd10e8bcf59b9af095a9f2ff8bdd7911356cdb5

Tx prefix hash: 56aea0f913e5836b3bcdf8a7211a2e26f100c5518e1c42d1e4cf11febdc8bbf1
Tx public key: f2f74acd6173aa09d6b91713f0eb2c872840a857adbdfd6820e604ac70fcbaa2
Timestamp: 1742951483 Timestamp [UTC]: 2025-03-26 01:11:23 Age [y:d:h:m:s]: 01:234:17:47:05
Block: 1247339 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 431759 RingCT/type: yes/0
Extra: 01f2f74acd6173aa09d6b91713f0eb2c872840a857adbdfd6820e604ac70fcbaa2021100000004a11dba98000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 226588708afbacb5530c230bb0e374246b45b9c3425ad4a5e4f43fd4ec2d16f4 0.000600000000 1734346 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": 1247349, "vin": [ { "gen": { "height": 1247339 } } ], "vout": [ { "amount": 600000000, "target": { "key": "226588708afbacb5530c230bb0e374246b45b9c3425ad4a5e4f43fd4ec2d16f4" } } ], "extra": [ 1, 242, 247, 74, 205, 97, 115, 170, 9, 214, 185, 23, 19, 240, 235, 44, 135, 40, 64, 168, 87, 173, 189, 253, 104, 32, 230, 4, 172, 112, 252, 186, 162, 2, 17, 0, 0, 0, 4, 161, 29, 186, 152, 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: