Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c16894cbc3f7ac513ae9df3ba2967b6c91bef1ae11a874b40e4902a0b91edaf9

Tx prefix hash: 68d3ecc5f5c1fadbafb07495101a9be5283cdc0fc47c8d5f2839c6f43c7237e1
Tx public key: 8c5976a2ca083023f25ac7832546b8d22a3ca2782e4e33153024a562d5075541
Timestamp: 1751064976 Timestamp [UTC]: 2025-06-27 22:56:16 Age [y:d:h:m:s]: 00:324:13:53:45
Block: 1314138 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 222526 RingCT/type: yes/0
Extra: 018c5976a2ca083023f25ac7832546b8d22a3ca2782e4e33153024a562d50755410211000000022609b3a0000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: f27966b919e11e7f05714b5f4c7468fdbfad75ed51f2b6555ed49e289f1c93ea 0.000600000000 1801783 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": 1314148, "vin": [ { "gen": { "height": 1314138 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f27966b919e11e7f05714b5f4c7468fdbfad75ed51f2b6555ed49e289f1c93ea" } } ], "extra": [ 1, 140, 89, 118, 162, 202, 8, 48, 35, 242, 90, 199, 131, 37, 70, 184, 210, 42, 60, 162, 120, 46, 78, 51, 21, 48, 36, 165, 98, 213, 7, 85, 65, 2, 17, 0, 0, 0, 2, 38, 9, 179, 160, 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: