Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 113435372c070fb7a42918569c730f3f65522088252ed9ae7362fb9e9ed02b26

Tx prefix hash: 15bee0f76ae89bf44741138c37e4f0e845323ce596949fd8bfc0f7364e100747
Tx public key: 1b3878de499b12c4a611e478a5da315238b7c511d72a124ff81170a70c4f77b5
Timestamp: 1727851012 Timestamp [UCT]: 2024-10-02 06:36:52 Age [y:d:h:m:s]: 00:112:10:27:44
Block: 1122645 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 80339 RingCT/type: yes/0
Extra: 011b3878de499b12c4a611e478a5da315238b7c511d72a124ff81170a70c4f77b502110000000491e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b03c5b3959ee90ef3963259d6c416e2a0e2a6b83d6964b013b018f7786f2e08e 0.600000000000 1605126 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": 1122655, "vin": [ { "gen": { "height": 1122645 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b03c5b3959ee90ef3963259d6c416e2a0e2a6b83d6964b013b018f7786f2e08e" } } ], "extra": [ 1, 27, 56, 120, 222, 73, 155, 18, 196, 166, 17, 228, 120, 165, 218, 49, 82, 56, 183, 197, 17, 215, 42, 18, 79, 248, 17, 112, 167, 12, 79, 119, 181, 2, 17, 0, 0, 0, 4, 145, 225, 60, 4, 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