Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 098f6de2d91fc71844fd9ab78d84573e24d19486003e2cb732f9b37bae06b80c

Tx prefix hash: aeef76831542636f414ff3df7a1dbc43f2dcd564e7c231360205b27307e47e98
Tx public key: 604a2ff888fc8134cae87d7839bdf1badf962aed94cd06360bb8df3fa9f47099
Timestamp: 1744246386 Timestamp [UTC]: 2025-04-10 00:53:06 Age [y:d:h:m:s]: 01:222:05:38:12
Block: 1258063 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 422876 RingCT/type: yes/0
Extra: 01604a2ff888fc8134cae87d7839bdf1badf962aed94cd06360bb8df3fa9f470990211000000076c98aa3d000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: d6a731c0844d23af865d1f06f22e5e565ecbb413a1542b136732b07beb77a6ff 0.000600000000 1745196 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": 1258073, "vin": [ { "gen": { "height": 1258063 } } ], "vout": [ { "amount": 600000000, "target": { "key": "d6a731c0844d23af865d1f06f22e5e565ecbb413a1542b136732b07beb77a6ff" } } ], "extra": [ 1, 96, 74, 47, 248, 136, 252, 129, 52, 202, 232, 125, 120, 57, 189, 241, 186, 223, 150, 42, 237, 148, 205, 6, 54, 11, 184, 223, 63, 169, 244, 112, 153, 2, 17, 0, 0, 0, 7, 108, 152, 170, 61, 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: