Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 59f78a10e7945abb451827680bf7ac3661bbf1b1fd23015904f2b2d321d06234

Tx prefix hash: 8a08608aa9c0bb1302de7f98b4317a44e415ce1cfd5060c414b8733563b6abe3
Tx public key: 5e6f66c20b805fbd2ac530db61aad3ca442a0e7856d7abfa6d0c8c0bc2d89171
Timestamp: 1704964560 Timestamp [UCT]: 2024-01-11 09:16:00 Age [y:d:h:m:s]: 01:078:04:16:23
Block: 932894 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 316965 RingCT/type: yes/0
Extra: 015e6f66c20b805fbd2ac530db61aad3ca442a0e7856d7abfa6d0c8c0bc2d8917102110000000c7a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 1fa0c29881ac53ff108ac023888e88a8e61980bdfa433171e2418d5a1a4ae1b6 0.600000000000 1390834 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": 932904, "vin": [ { "gen": { "height": 932894 } } ], "vout": [ { "amount": 600000000, "target": { "key": "1fa0c29881ac53ff108ac023888e88a8e61980bdfa433171e2418d5a1a4ae1b6" } } ], "extra": [ 1, 94, 111, 102, 194, 11, 128, 95, 189, 42, 197, 48, 219, 97, 170, 211, 202, 68, 42, 14, 120, 86, 215, 171, 250, 109, 12, 140, 11, 194, 216, 145, 113, 2, 17, 0, 0, 0, 12, 122, 156, 244, 199, 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