Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d357851eccc2896ffc4c9b6d25d8e9bd954786ef598a27b45bc0bd1b996cf1fd

Tx prefix hash: 4c828e8c0825055cd4bc1ec208525d6394f1feabcc7ccbfe5d7fe2ea738dd50f
Tx public key: f28febf44c4a9517f51467871e7ead66fc800553a6c7077a082a2dea46ae79d8
Timestamp: 1710590464 Timestamp [UCT]: 2024-03-16 12:01:04 Age [y:d:h:m:s]: 00:349:08:24:20
Block: 979566 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 249753 RingCT/type: yes/0
Extra: 01f28febf44c4a9517f51467871e7ead66fc800553a6c7077a082a2dea46ae79d802110000000d59dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e42796f243ff6bc9d3b6c9ca5eb02cf8ea1bf21559834731f70db22380b99d06 0.600000000000 1439603 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": 979576, "vin": [ { "gen": { "height": 979566 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e42796f243ff6bc9d3b6c9ca5eb02cf8ea1bf21559834731f70db22380b99d06" } } ], "extra": [ 1, 242, 143, 235, 244, 76, 74, 149, 23, 245, 20, 103, 135, 30, 126, 173, 102, 252, 128, 5, 83, 166, 199, 7, 122, 8, 42, 45, 234, 70, 174, 121, 216, 2, 17, 0, 0, 0, 13, 89, 218, 211, 245, 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