Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c0a04475bf25b2d4288cc2c334b4c9895b0426117e9e01edb18b03824c9f89fa

Tx prefix hash: a0bdb7bce466939cadc2c5d3432804c883bc940e7a0d356731141c626401c5f8
Tx public key: 10f30932a5e2747898746889b615983e7759d2408396d123461ead527eb71fe5
Timestamp: 1735507292 Timestamp [UTC]: 2024-12-29 21:21:32 Age [y:d:h:m:s]: 01:132:07:56:28
Block: 1185981 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 345548 RingCT/type: yes/0
Extra: 0110f30932a5e2747898746889b615983e7759d2408396d123461ead527eb71fe50211000000071f0a53eb000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 2dbae3562b195ef56a0b3ee0aa993db37c9139dd7cb645fdb98adfe71d4aa34c 0.000600000000 1672456 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": 1185991, "vin": [ { "gen": { "height": 1185981 } } ], "vout": [ { "amount": 600000000, "target": { "key": "2dbae3562b195ef56a0b3ee0aa993db37c9139dd7cb645fdb98adfe71d4aa34c" } } ], "extra": [ 1, 16, 243, 9, 50, 165, 226, 116, 120, 152, 116, 104, 137, 182, 21, 152, 62, 119, 89, 210, 64, 131, 150, 209, 35, 70, 30, 173, 82, 126, 183, 31, 229, 2, 17, 0, 0, 0, 7, 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: