Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c1600739d577f920b0af3a9358af5ffeb8fc2a0771576a4baab2ca5257a67846

Tx prefix hash: 9b95326525d7f109e0a7442e3eebcb42745da0f0fef6f065cc6ca0a9ef794a22
Tx public key: c69196eb753f9b9b4fd6a7df12dda9209fbafd77ef6f7405d09d0e25c38368c8
Timestamp: 1709178800 Timestamp [UTC]: 2024-02-29 03:53:20 Age [y:d:h:m:s]: 02:266:15:14:11
Block: 967849 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 715645 RingCT/type: yes/0
Extra: 01c69196eb753f9b9b4fd6a7df12dda9209fbafd77ef6f7405d09d0e25c38368c802110000000459dad3f5000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 6de5cf8ed5ede66cc3c0352dbd7a14eea541d662e80382c0bbd642de5a8651cd 0.000600000000 1427640 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": 967859, "vin": [ { "gen": { "height": 967849 } } ], "vout": [ { "amount": 600000000, "target": { "key": "6de5cf8ed5ede66cc3c0352dbd7a14eea541d662e80382c0bbd642de5a8651cd" } } ], "extra": [ 1, 198, 145, 150, 235, 117, 63, 155, 155, 79, 214, 167, 223, 18, 221, 169, 32, 159, 186, 253, 119, 239, 111, 116, 5, 208, 157, 14, 37, 195, 131, 104, 200, 2, 17, 0, 0, 0, 4, 89, 218, 211, 245, 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: