Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 042d2772623e9485dbf8df3323b56f4bc284ce1d1af99a09088a0551a4dc2a86

Tx prefix hash: 9847619f5d4ba9dd1325a1c0a5127d04c8ca77c804799dd3b438874f370e5639
Tx public key: 6a431c3c5f89321ef390086577be71a83569a15cbe11f4e5cfc6d2a518043bc7
Timestamp: 1705443100 Timestamp [UCT]: 2024-01-16 22:11:40 Age [y:d:h:m:s]: 01:152:23:05:40
Block: 936853 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 370345 RingCT/type: yes/0
Extra: 016a431c3c5f89321ef390086577be71a83569a15cbe11f4e5cfc6d2a518043bc702110000000452d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b5e8392593d1b824d1adbdbf5554a506062b7864011a8e18c0d3f35f5cfd0af0 0.600000000000 1394895 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": 936863, "vin": [ { "gen": { "height": 936853 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b5e8392593d1b824d1adbdbf5554a506062b7864011a8e18c0d3f35f5cfd0af0" } } ], "extra": [ 1, 106, 67, 28, 60, 95, 137, 50, 30, 243, 144, 8, 101, 119, 190, 113, 168, 53, 105, 161, 92, 190, 17, 244, 229, 207, 198, 210, 165, 24, 4, 59, 199, 2, 17, 0, 0, 0, 4, 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