Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1f1181a23dc74fdd03b3584efcff0ed219f40b5b743fa0cdb53041d4ce98d979

Tx prefix hash: 9e812670d6ddd53e42e93117c7ebf88f56d387c7a48eb67b06a39d41d3a1ad18
Tx public key: 92e42c6ea5e179f4a65f590a25075c235e2d69dbe220aee171e9775f569be822
Timestamp: 1697409969 Timestamp [UCT]: 2023-10-15 22:46:09 Age [y:d:h:m:s]: 01:131:21:20:01
Block: 870478 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 355244 RingCT/type: yes/0
Extra: 0192e42c6ea5e179f4a65f590a25075c235e2d69dbe220aee171e9775f569be8220211000000014b8f5122000000000000000000

1 output(s) for total of 0.801207600000 dcy

stealth address amount amount idx
00: 105707fc822b3a5b17ad16c867be6e870b48bc39c006ec6b6b11401ca0c3548c 0.801207600000 1325357 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": 870488, "vin": [ { "gen": { "height": 870478 } } ], "vout": [ { "amount": 801207600, "target": { "key": "105707fc822b3a5b17ad16c867be6e870b48bc39c006ec6b6b11401ca0c3548c" } } ], "extra": [ 1, 146, 228, 44, 110, 165, 225, 121, 244, 166, 95, 89, 10, 37, 7, 92, 35, 94, 45, 105, 219, 226, 32, 174, 225, 113, 233, 119, 95, 86, 155, 232, 34, 2, 17, 0, 0, 0, 1, 75, 143, 81, 34, 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