Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ec919ecec3bd83bf0af887808c5161689ccedb16c66053fb8410a04cf1bdce32

Tx prefix hash: 405ace42b0859fe2ac802678b023775dd0eb77201f780b0c0d465a1356a10401
Tx public key: 03a8a10995e76cb40c59cb5b24da62896f2fdcf20947d9b60c15d21ca590192d
Timestamp: 1583538929 Timestamp [UCT]: 2020-03-06 23:55:29 Age [y:d:h:m:s]: 04:268:00:09:15
Block: 77918 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1085976 RingCT/type: yes/0
Extra: 0103a8a10995e76cb40c59cb5b24da62896f2fdcf20947d9b60c15d21ca590192d0211000000124ac5aa02000000000000000000

1 output(s) for total of 338.708514158000 dcy

stealth address amount amount idx
00: 9a4ca91f29a86256d4828d0600aab7087aafcd1b44fa5f8c1cb5fab9b57799ee 338.708514158000 143163 of 0

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": 77928, "vin": [ { "gen": { "height": 77918 } } ], "vout": [ { "amount": 338708514158, "target": { "key": "9a4ca91f29a86256d4828d0600aab7087aafcd1b44fa5f8c1cb5fab9b57799ee" } } ], "extra": [ 1, 3, 168, 161, 9, 149, 231, 108, 180, 12, 89, 203, 91, 36, 218, 98, 137, 111, 47, 220, 242, 9, 71, 217, 182, 12, 21, 210, 28, 165, 144, 25, 45, 2, 17, 0, 0, 0, 18, 74, 197, 170, 2, 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