Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 80280619df2444ec5b1c2f2febc2f511cd42913bb2802f8cb5d2e2356d88878f

Tx prefix hash: d1a1a6d468186c0b7a7d936ce02c3a04896f15c002a7ec5df7ff3dbd941d96bb
Tx public key: 934be597d0855d11d01e4fc473ab7c48ead2e5e90710695236b577361d8f7875
Timestamp: 1736290073 Timestamp [UTC]: 2025-01-07 22:47:53 Age [y:d:h:m:s]: 01:311:21:26:51
Block: 1192470 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 486665 RingCT/type: yes/0
Extra: 01934be597d0855d11d01e4fc473ab7c48ead2e5e90710695236b577361d8f7875021100000007007f978a000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: b06095822b316167fec902ec20d1e17ddff41f7278f687757b668193d9f7a676 0.000600000000 1679023 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": 1192480, "vin": [ { "gen": { "height": 1192470 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b06095822b316167fec902ec20d1e17ddff41f7278f687757b668193d9f7a676" } } ], "extra": [ 1, 147, 75, 229, 151, 208, 133, 93, 17, 208, 30, 79, 196, 115, 171, 124, 72, 234, 210, 229, 233, 7, 16, 105, 82, 54, 181, 119, 54, 29, 143, 120, 117, 2, 17, 0, 0, 0, 7, 0, 127, 151, 138, 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: