Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0f1e5db82f5cac16f570280d0b79c0754f070398dd8c06909faf45caf3278ba0

Tx prefix hash: aa9e09294accd098a0f9b764909c235af9f7be71e0a117c53dac10d0037ee3fb
Tx public key: a7c5ccde38da0098792caa2ecd3b27b334653dbb232b0ef4ce1264e84c041da3
Timestamp: 1728188586 Timestamp [UCT]: 2024-10-06 04:23:06 Age [y:d:h:m:s]: 00:159:10:49:47
Block: 1125442 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 113759 RingCT/type: yes/0
Extra: 01a7c5ccde38da0098792caa2ecd3b27b334653dbb232b0ef4ce1264e84c041da302110000000491e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: c5cc271bd031d64a58cc93ef63d24392754be1f7b7c0af914e53e0d51817f95e 0.600000000000 1608191 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 dinasty-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": 1125452, "vin": [ { "gen": { "height": 1125442 } } ], "vout": [ { "amount": 600000000, "target": { "key": "c5cc271bd031d64a58cc93ef63d24392754be1f7b7c0af914e53e0d51817f95e" } } ], "extra": [ 1, 167, 197, 204, 222, 56, 218, 0, 152, 121, 44, 170, 46, 205, 59, 39, 179, 52, 101, 61, 187, 35, 43, 14, 244, 206, 18, 100, 232, 76, 4, 29, 163, 2, 17, 0, 0, 0, 4, 145, 225, 60, 4, 0, 0, 0, 0, 0, 0, 0, 0, 0 ], "rct_signatures": { "type": 0 } }


Less details
source code | explorer version (api): master-2022-04-20-3036769 (1.2) | dinastycoin version: 4.1-b41cfa2b8