Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: daae9c35dc848a939bef63f2e289b694d78a4a773ed171f84c6b5793391bec97

Tx prefix hash: b2bab5d3216bbc58aec158e5e9b6a7f25393d67170d79a0e4e872df86cef9bde
Tx public key: a05157ce1714fb87c223ae9b046062374e613f6e8b88a901ef0011d780215b43
Timestamp: 1715859814 Timestamp [UCT]: 2024-05-16 11:43:34 Age [y:d:h:m:s]: 01:177:21:28:01
Block: 1023231 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 385749 RingCT/type: yes/0
Extra: 01a05157ce1714fb87c223ae9b046062374e613f6e8b88a901ef0011d780215b4302110000000252d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f29358fba38d3a862431b26ec07c24cc0021fef7805dc05a527a84809e538a80 0.600000000000 1488076 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": 1023241, "vin": [ { "gen": { "height": 1023231 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f29358fba38d3a862431b26ec07c24cc0021fef7805dc05a527a84809e538a80" } } ], "extra": [ 1, 160, 81, 87, 206, 23, 20, 251, 135, 194, 35, 174, 155, 4, 96, 98, 55, 78, 97, 63, 110, 139, 136, 169, 1, 239, 0, 17, 215, 128, 33, 91, 67, 2, 17, 0, 0, 0, 2, 82, 212, 126, 148, 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